-
When a fraud submission is made on a rollapp, there needs to be a defined way to handle the existing records of aliases tied to the rollapp in question.
Two possible solutions are:
1. Move all ali…
-
see also https://github.com/dymensionxyz/dymension-rdk/issues/467
cc @zale144
danwt updated
2 weeks ago
-
After the upgrade, there is a notion of canonical port/channel
Need to make sure existing chains are not broken by this upgrade
danwt updated
2 weeks ago
-
Edit Aug 20th: this not really necessary since RollApp can now buy alias/handle.
-
Due to bridging fee and the lazy claim process we should for now disable the ability to use PFM From rollapp.
-
based on:
1.https://www.notion.so/dymension/Rollapp-Light-Client-Validity-Vanilla-TrustPeriod-42c84ea2e9fd4b67a53f3636f7ec5687?pvs=4
2. https://www.notion.so/dymension/Light-client-rollback-dd9984a422…
-
we need the following changes:
add display_name to the rollapp metadata (updatable at any time by rollapp owner like other metadata fields)
when showing a rollapp (dymd q rollapp show) -> we don’t r…
danwt updated
2 weeks ago
-
### Implementation ideas
Hello Dymension Team, I am an engineer from debank. We would like to deploy a contract on the EVM chain, but currently, we don't have the necessary permissions. Can you assis…
lhypj updated
2 weeks ago
-
Currently if one rollapp finalization fail we fail the entire rollapps finalization.
We should fail it on a per rollapp basis.
-
As a general framework setup, we should always test with multiple rollapps running and :
1. states are finalizing
2. IBC packets are being relayed (automatic relaying as a background process for ea…