Could be done as a prettifying step in the optimizer or in the printer, or both.

The printer should not just change the kind of literal.

Is your feature request related to a problem? Please describe.
Cicero server only supports a single version of the cicero trigger call through the /trigger endpoint. It might be interesting to extend the cicero server API to the rest of the commands (e.g., draft invoke parse).

Other improvements could include the ability to pass or create the template from a string (binary encode

Update the compiler version for the Auction Example to 0.5.0 so we can use abi.decode. Currently not possible until the OpenZeppelin folks update their code to use the newer compiler version. On-hold, but should be an easy change

openzeppelin-solidity/contracts/access/roles/MinterRole.sol:1:1: SyntaxError: Source file requires different compiler version (current compiler is 0.5.0+commit.1d

After #326 is done we can make a full RPM package.

This issue is for tracking various things that we should document:

• "I can envision a scenario where a given client wants to prove that a transaction at index x of block y is not transaction z, but instead is transaction z'. I guess this would simply be a proof of inclusion of transaction z' and the business logic around z and z' would have to be handled at a higher customer/library consumer c

There are plenty of big numbers represented as strings in nearcore RPC since JS does not support big integer types (u64, u128), but there are also many numbers currently incorrectly represented as JS numbers (I consider it to be a major bug in nearcore RPC, which has to be fixed before mainnet).

It makes a lot of sense to expose these values as big numbers. It is going to be a breaking change f

Description
When I log with nano ledger, then log out and switch to metamask, backend responds with 403 on create attempt. Metamask signer is launched correctly but nano ledger UI is visible

Environment
Found on stage, logging with nano ledger then switching to metamask

Right now the example app does not notice errors on rpc calls and does not report them to the user