noble-assets / noble Goto Github PK

This PR needs to be partially rolled back: #88

https://www.notion.so/strangeloveventures/Noble-CCTP-rev-2-dbd924e01d004a56b427f5765883d1b6#f6c7d4bab14d478cbc55c0134710aeec

Story is finished when Circle has signed off on design https://www.notion.so/strangeloveventures/Noble-CCTP-rev-3-8b3064b246914348a506abb8817380ad#c8912a64e43c4d0fb27b370c6e52bcc4

I cannot make install the noble repo.

I checked that the inport doesn’t have a b40c4c394865 commit anymore.

changed the corresponding import at go.mod to http://github.com/strangelove-ventures/paramauthority v0.1.0 and go mod tidy and it build now

• Param Authority will have 1000 stake tokens
• 6 validators
• Each validator will have one token delated to them from Param Authority account

When this happens, the chain validators are producing blocks fine, but the state cannot be queried, so operations such as queries, tx broadcasts, and state exports all fail.

exit code 1:  Error: rpc error: code = InvalidArgument desc = failed to load state at height 7; version does not exist (latest height: 7): invalid request

This happens when running queries against a prior height (non-latest) also.

This can be reproduced in the ibctest case here, but has also been reproduced outside of ibctest

### Tasks
- [ ] https://github.com/strangelove-ventures/noble/issues/225
- [ ] https://github.com/strangelove-ventures/noble/issues/226

verify pausing also prevents transfers, burning, and configuring minters (while allowing removing minters).

Details: https://github.com/centrehq/centre-tokens/blob/master/doc/masterminter.md

Can you please add support for a MinterController role which would be responsible for controlling a single minter (1-1)
The MinterController should be able to configure the minter allowance and remove the controlled minter.
The MasterMinter role should be updated to configure(controller, minter) and remove a minter controller.

Need assistance from testnet runners to assure a "yes" vote as voting period is only 60s.

• [-] refactor Noble so we can add another tokenfactory
• upgrade noble in testnet

https://www.notion.so/strangeloveventures/CCTP-detailed-spec-f65af1e6a5884517a2ec4b228a56ebad

Ready for the Thursday Circle meeting

The upgrade hander should accommodate this PR: #127.

How are we selecting members of multi-sig?

Need to:
Deliver to Circle

Can we do the noble node set up using docker ?

Any specific community where we can post our queries .

For example,

message Admin {
  string address = 1; 
}

Wraps an address, but it might as well have been a regular string value.

In a map-like structure in the KV store, we're using the address as part of the key, but the value stored at that key is just the same addressed wrapped in a named proto. In terms of storage we wouldn't need anything more than a mapping of an address key to a single-byte bool.

In the original notion docs it says that the "Master Minter" has the privledge to remove a minter.

Currently, only the "Mint Controller" account has the privilege to remove a minter.

In case we end up not having any messages to handle.

With development mostly done we can rip out the dep on ignite-cli. AFAIU it's a necessary step before introducing the consumer chain capabilities anyways.

The unit tests leave a lot to be desired in general. Naming conventions are unintuitive and there are some things that could be made much more straightforward and easy to work with

Right now the master minter can set any amount and any denom as an allowance. Maybe the denom has to be set somewhere globally to ensure that if a master minter decides to set allowance as "100000foo" the chain will throw an error.

As more tokenfactory modules are added, they can all use the same block middleware.

as long as we can block all outgoing transfers (IBC and non-IBC) and all incoming non-IBC transfers we should be OK.

Scenario: Strangelove will implement a CCTP Relayer that enables the following use case:
  When a User initiates token burn on ETH using dYdX App
  Then IBC forwarding information is (optionally) included in the message metadata
  When ~13 minutes elapse for burn finality on ETH
  Then Strangelove CCTP Relayer observes burn on ETH
  And requests Attestations from Circle API 
  And manages retry handling for block observation errors and attestation request errors
  When Circle API proves burn and issues attestation
  Then Strangelove CCTP Relayer broadcasts tx to Noble chain with attestations (with retry handling on broadcast errors)
  And Noble chain validates attestations, performs mint, then initiates IBC forward if specified

Design here

### Tasks
- [ ] https://github.com/strangelove-ventures/noble/issues/221
- [ ] https://github.com/strangelove-ventures/noble/issues/219
- [ ] https://github.com/strangelove-ventures/noble/issues/220
- [ ] https://github.com/strangelove-ventures/noble/issues/224
- [ ] https://github.com/strangelove-ventures/noble/issues/222
- [ ] https://github.com/strangelove-ventures/noble/issues/223
- [ ] https://github.com/strangelove-ventures/noble/issues/218
- [ ] https://github.com/strangelove-ventures/noble/issues/120
- [ ] https://github.com/strangelove-ventures/noble/issues/230