cashscript
cashscript copied to clipboard
⚖️ Easily write and interact with Bitcoin Cash smart contracts
Instead of placing all contructor params at the beginning of the contract, the compiler could auto-insert the params at first usage. This would be a nice default, resulting in optimized...
A good refactor would be to abstract stack pushing/popping in compiler 'GenerateTargetTraversal.ts' from June 2023 discussion: > I agree it's confusing. It might be good to abstract away the stack...
Currently a contract's constructor-inputs are kept in the artifact as `constructorInputs`, and not repeated in the `bytecode` property on the artifact because they are assumed to be put in front...
after finishing #172 there are still refactors of the code that we want to do - [ ] Make bitauthUri required in FailedTransactionError once the advanced transaction builder supports debugging...
currently the debug tooling operates on the unoptimized bytecode which has been a source of confusion for developers familiar with the low level workings. For better support for hand-optimization of...
bool b, bool a; `a == b` should compile to OP_NUMEQUAL (rather than OP_EQUAL) `a != b` should compile to OP_NUMNOTEQUAL (rather than OP_EQUAL OP_NOT)
this PR changes the following: - improved getting started - added Cauldron DEX to examples, remove transferWithTimeout - moved operators section to types page - improved notice on pragma usage...
consider adding arguments to MockNetProvider to change the taget environment (chipnet vs mainnet vs experimental VM)
if we make the `electrum` client on ElectrumNetworkProvider public then users could use subscriptions to addresses/blockheights without needing a separate electrum client with the `electrum-cash` library directly. we need to...
v0.11.0
This is a WIP PR that includes all the work done for the coming v0.11.0 release