Rosco Kalis
Rosco Kalis
Allow variables and parameters to have an `unused` modifier that indicates it is ok for them to be unused. ```solidity contract Test(int unused a, int b) { function test(int c)...
Currently the only variables that are accessible to *all* contract functions are the constructor parameters. However, it might be useful to have some variables that are not necessarily constructor *parameters*,...
Sometimes transactions need to be signed by multiple people (e.g. multisig). In these cases it should be possible for people to sign their part of the transaction and leave the...
See comments in #98 We can add an `OP_CODESEPARATOR` between the constructor args and the bytecode. This should make it easier to make "state simulated" contracts. Since then `OP_ACTIVEBYTECODE` would...
The main primitive used in Libauth's flexible transaction generation API is the AuthenticationTemplate. It would be useful if the CashScript SDK enables a Contract instance to export a libauth template...
Libauth has a builtin VM implementation that can be used to locally evaluate a transaction before sending it to the network. We use this in the automated tests for AnyHedge...
Structs can be defined by the implementer of a contract like this: ``` struct PriceMessage { bytes4 blockheight; bytes4 price; } ``` The CashScript SDK can automatically serialise JSON data...
Currently the AST includes nodes of the type FunctionCall, which are things like `max(int, int)`. These "functions" are currently stored inside a global symbol table, but since they are essentially...
In #18 I listed several potential compiler optimisations of which the lowest hanging fruit was implemented in `0.2.0`. The remaining optimisations are documented below, although this list might be updated...
When passing in any of the following: ``` truffle run verify --arg1 0000 truffle run verify --arg1 0x0000 truffle run verify --arg1 "0000" truffle run verify --arg1 "0x0000" truffle run...