Brice
@juliencarbonnell as an alternative to a graphical front-end until this gets re-added to the explorer, you can write some simple node.js scripts to interact with your contract via the command...
I also think this can be closed.
Not directly, but the endpoint to retrieve a block returns all the information you need: ``` "execution_cost_read_count": 2477, "execution_cost_read_length": 1659409, "execution_cost_runtime": 2520952000, "execution_cost_write_count": 608, "execution_cost_write_length": 80170, ``` The maximum values...
@lnow Members of the Technical CAB have requested your input on this SIP.
I'm comfortable with the masking behavior currently described in this SIP, or the behavior I originally had, where a shift amount > 128 will just clear all the bits and...
> I see the symbols have changed. Is that the feedback from the technical CAB? Exactly.
The situation was that it was a last minute contribution from a community member and it seems like a non-controversial add on, and therefore not worth the effort of a...
Yes, see @wileyj's message above. I sat this one out since I was the author and @wileyj took the lead.
I agree this would be very valuable. I'd love to see something included that would allow wallets and explorers to show details about errors as well. For example, something like:...
I do like the idea of having the contract point off-chain for detailed documentation, but what would be the argument for having some structured on-chain documentation and some off-chain? Is...