E2E test of Pente<->Noto integrated tokens with Bond sample

[peterbroadhurst]

• In PR chain with Coordinator selector / delegation policy for 100% endorsment domains #329
• Depends on Allow formatting of string errors separately from matching hyperledger/firefly-signer#85

Summary

Provides Domain-specific receipt information for completed transactions:

• ptx_getTransactionReceipt - no change to content, but now available on all nodes
• ptx_getStateReceipt - provides information about the the input/read/output/info states for a TX
  • Tells you if there are states associated with that TX that you do not know about
  • TODO: Nullifiers need to be added here later
• ptx_getDomainReceipt - gives domain specific information about private transactions
  • For Pente gives you a transaction with the Ethereum transaction and receipt with an Ethereum receipt
  • The payload of both is as similar as possible to standard Ethereum, but is a subset
• ptx_getTransactionReceiptFull - includes states and domainReceipt
  • Has domainReceiptError if unavailable, rather than erroring
• ptx_call - now fully wired up for Pente private EVM contracts as well as public smart contracts
• Utilities for decoding ABI encoded data using the dictionary of ABIs in Paladin (via ptx_upsertABI and sending txs):
  • ptx_decodeError
  • ptx_decodeCall
  • ptx_decodeEvent
  • ^^^ integrated into UI for private EVM Transactions if you upload the ABIs

Includes significant work from @awrichar in demonstrating the use of a Pente private EVM smart contract for sophisticated notarization of a Noto based token modeling a Bond.

• See Add a bond test using Noto+Pente #335

Detailed work list built as I went through

• Add recording of read states through Proto, Domain and State Manager
  • This is needed as we want
• Build an API on State Manager to query all states for a confirmed transactions
  • Needs to handle DB complexity over the three tables we have (the three tables make state query function)
  • I've used a UNION ALL combined with RIGHT JOIN construct to join things on the DB side
  • Had to jump through some hoops to make this work for GORM
• Provide a spelling so consumers of this API can know if all the states are available or not
• Change the way Unit Test DBs are manager for Postgres
  • Check that the migrations delete all the DBs they create
  • Use a predictable DB per package (rather than one per test) - much easier to use psql to debug now 😅
  • Clean down the DB using DELETE FROM instead of DROP DB between tests - ⏩ test execution
• Refactor Pente assembly ...
  • Transactions are now signed as part of building the ETH_TRANSACTION encoded EIP-1559 payload
  • The encoded+signed rawTransaction is what is written into the new info state
  • The info state also includes evmVersion, baseBlock and bytecodeLen which are the execution context
  • Ensure all states have 🧂
  • All the things in Wires up ptx_call for private transactions, and works through ERC-20 transfer E2E #344
  • @awrichar's things from pente: add support for pre-approval of transitions #345
• Build generic interface on to_domain proto interface to construct a receipt
  • This required introduction of a new info type of state emitted from a transaction
  • This type is not required to be available on-chain before the transaction
  • It is also not required to be available on-chain for subsequent transactions
  • It is written to the database and distributed as part of the transation
  • It is passed to Endorse and Receipt flows with the Domain
  • Thus it can be used to contain things like the Pente signed input of the transaction that is required for execution

  • Interesting that until this point, this thing that used to be the only thing Tessera wrote, was missing from our TXs that only recorded the chain input/output state, and not explicitly the signed input payload from the submitter.

• Allow receipts to be stored, without the corresponding transaction
  • Includes adding domain to the receipts
  • This means that there is information available on other nodes that can be queried
  • This is different from base ethereum where you get the TX inputs and receipts, but I'm currently convinced this difference is justified
  • In the case of Pente, the receipts contain both the inputs + outputs of the transaction
• Build a ptx_getTransactionReceiptFull or similar interface to call this
• Implement for Pente - giving an near-identical to Ethereum receipt
  • Include contractAddress for deploys - unblocks E2E work
  • Include full EVM Event details
  • This included updating our execution to accumulate logs across all the executed frames, with the source address
• Adds the function to allow a combined Noto<->Pente chained private transaction
  • See Private transaction chaining for Noto<->Pente interactions #346
• Implement for Noto + Zeto (minimal)
  • Minimal is determined to be a suitable message for now
• Add prepared transaction support
  • See Support prepared transactions fully on the JSON/RPC of Paladin #349
• Various key manager enhancements
  • See Key manager enhancements #350
• Updated deploy interface into Domains to have access to from information
  • See Add a from into the context of deploys #353
• Added JSON/RPC APIs for decoding calls and events, as well as errors
  • See Add JSON/RPC APIs to decode calls and events from the dictionary, alongside errors #354
• Added UX for seeing inside the private EVM using ^^^ APIs
  • See Add Private EVM decoding to UI #355
• Adds UI to build
  • See Adding UI api to Paladin #348

[hosie]

LGTM