Silas Davis
Silas Davis
Come to think of it, it's not clear to me why we don't control deletion entirely from the projection spec, there's not really any need for the marker field. I...
I should have originally remembered we do of course have 2, 3, 4 already implemented. There was some prior work done for `0x1` - https://github.com/hyperledger/burrow/pull/777. Unfortunately that could not get...
I am copying this in from chat.hyperledger.org for visibility from @madiazp: > burrow has implemented the byzantium/constantinople hard fork? what will happen with the istambul one? Yes Burrow should have...
> Ok, So the contracts that will be included are the Istambul ones. Yep that's what we should aim for generally.
There is still value in doing this, I don't think it should be closed purely because inactive
I don't entirely follow some of the wording in story A, but I think I get the gist. We discussed the ability to schedule transactions for the proposal mechanism, so...
I think this still represents useful functionality for Burrow to host
Can you provide the code you would like to work? It is not clear from your example.
This could do with being documented. There are three ways to change permissions currently: 1. Using permission SNatives via smart contract (provided the callee has appropriate setBase/setGlobal moderator permissions) 2....
Part 1 of this is done 2 and 3 should probably be separate tickets