Artem Chystiakov
@Arvolear
Ethereum OG | Simplicity Ecosystem Engineer at @blockstream | Opinions are my own
191 Following 2.8K Followers
Simplicity-powered decentralized price oracle on Liquid concept.
We've also built a full PoC with SimplicityHL smart contracts and an interactive UI. Setup a multisig, create proposals, vote, and execute them. Never leaving a dapp.
This may be controversial and not privacy-preserving in the best way, but I still want to share this idea.
A multisig protocol where it is just you, the front end, and the chain. No downtime. No other off-chain medium or service. Where Simplicity enables custom policy enforcement rules and multisig spending conditions.
This is a very early experiment to showcase what can be developed with Simplicity. Thus, the paper is not affiliated with Blockstream.
Show more
This may be controversial and not privacy-preserving in the best way, but I still want to share this idea.
A multisig protocol where it is just you, the front end, and the chain. No downtime. No other off-chain medium or service. Where Simplicity enables custom policy enforcement rules and multisig spending conditions.
This is a very early experiment to showcase what can be developed with Simplicity. Thus, the paper is not affiliated with Blockstream.
Show more
No bullshit deep dive. From low-level operability to common attack vectors on smart contracts.
I love OP_RETURN and there are genuinely great ways to use it.
By the way, there is now a Simplicity forum. If you are building something worth sharing, please do.
Some common Simplicity contract vulnerabilities. Though, the list is still very incomplete and will probably be expanded.
A highly optimized BIP-340-compatible Solidity library (yes, Solidity library) for Schnorr signature verification using sha256 and ecrecover precompiles. Costs only 6567 gas.
One step closer to UTXO covenants on Ethereum. Who's working on that?
At last @ethereum is solving one of it's biggest problems. UTXOs let's fucking go!
Auditing Simplicity contracts #5#.
Even if all the unit tests are passing, the contract may still be critically vulnerable. Watch out for deadlocks, it's very easy to miss edge-case conditions.
Show more
Aaand, it got solved! The challenge was to find a hidden mnemonic in the Taproot leaves of the 12 provided UTXOs. Will definitely create another CTF in the future, but much more difficult this time. So stay tuned. Congratulations to the solver!
Show more
Announcing the first-ever Simplicity CTF challenge!
I've locked 0.01 LBTC in a contract. Your task is to find how to unlock it and claim the reward!
I've also sent this challenge to our internal Blockstream chat.
Here is the description. Good luck!
Show more
Simplicity will eventually become available natively in Bitcoin. Maybe in 10 years. But that's the whole point.
You can now develop custom Simplicity libraries via Simplex framework. Just shipped dependency management and installation there. Working on covenants fuzz testing next.
We've just released SimplicityHL v0.6.0. Introducing imports, modules, dependencies, and source code flattening. Also, custom jet environments can now be implemented as dynamic libs and plugged into the compiler. Check out the full release!
Show more
We've just released SimplicityHL v0.6.0. Introducing imports, modules, dependencies, and source code flattening. Also, custom jet environments can now be implemented as dynamic libs and plugged into the compiler. Check out the full release!
Show more
Damn vulnerable Simplicity covenants #4#.
Timelocks are ambiguous. Nodes interpret them differently depending on the tx value passed. If v < 500_000_000, it's a block height; otherwise, it's a timestamp.
Be careful designing locking covenants. Unexpected unlocks may occur.
Show more
Damn vulnerable Simplicity covenants #3#.
Use `jet::sig_all_hash()` to construct transaction topology messages properly. Otherwise, it's fairly easy to allow signature replay attacks.
Show more
A small team can build magnificent things.
Damn vulnerable Simplicity covenants #2#.
Make sure that an attacker can't alter the transaction topology to bypass the assertions. In this example, checking that the Vault always sits in the "zero input" is critical.
Show more
