Junha Yang(양준하)
Junha Yang(양준하)
- [ ] Rename `simperby-common` to `simperby-core` - [ ] Rename `simperby-node` to `simperby`
Those two crates will be imported by the contract side, so there must be no dependencies that breaks WASM compatibility. Having a CI pipeline that checks such integrity would help.
You will need conditional compile using cargo `feature`
`RawRepositoryImpl` should be renamed to `RawRepository` and implement the method directly (not as a trait) I think we don't have another implementation of it.
We have multiple uses of `fetch`, which sounds more appropriate in `update`
A Simperby node should provide the local repository (which it manages) to the user so that he can update the `work` branch, while protecting other reserved branch and tags. There...
The message should be from one of the peers (`Config::peers`) Otherwise, DMS reject the message.
- The current status - Future plans
e.g., `TransferFungibleToken::token_address`, `TransferFungibleToken::receiver_address`, ..