Zeebit Questions & Feedbacks

[GabrielePicco]

Randomness

• They have implemented an oracle which listen to event and provides randomness on demand, trough an invoked callback
• This could potentially work effortlessly in the ER.

Discussion

• Can we internalize the Oracle
• If not, can we keep there Orcale close to the validator?

Cluster delegated accounts in the ER

• There are use-cases which require the delegated account to live in the same ER instance.

Discussion

• A discussed possible solution is to allow to specify a "group id", which group delegated accounts in the same validator

Persistent DA

• Zeebit and other would like to have a persistent link to access transaction after the Ephemeral Rollups has been shut down
• This requires a to maintain the ledger stored at all times

Discusssion

• Feasiblity
• Possible approaches

Delegation

Undelegation currently is done trough a transaction sent to mainnet. The delegation program then CPI into the original owner program in order to reset the PDA owner program.

Discussion

• We may need to change the flow and ensure that the undelegation first goes trough the ER, or make the ER commit the latest state and undelegate. This would prevent cases where the undelegation is done and we are not sure the latest state has been committed

Update Read Only accounts

• See: feat: Trigger instruction to update readonly account #59