Needing clarification for oryy.io Multisig

Oryy team has deployed an unofficial version of SAFE , the most secure multi-sig wallet in the web3 ecosystem. I’ve received a couple of questions from the community regarding the deployed version(v1.16): Oryy.io

  1. Smart contracts are not verified on the Explorer.

  2. Since the contracts are upgradable, who has the permission to upgrade?

  3. the mobile application does not work with the XDC network.

  4. Some off-chain components do not exist and show 404 from the backend response.

Multi-sig infra plays a crucial role in bringing additional security layer for builders to maintain permission part of their system including Treasury, Smart contract Upgrade, etc. for any individual delivers a no-code tool to secure their bag instead of keeping it on only non-custodial wallets like Metamask, Ledger, etc. Especially when it comes to DeFi it’s a cornerstone of financial services on Blockchain and end-users/institutions’ liquidities are involved.

Moreover, it gives the developers and builders no concerns and get onboard easier, especially for products migrating from other EVMs to the XDC Network that are expecting the same infra.

Furthermore, at least one Safe version can be hosted like the following pattern on one of official subdomains of XDC or Xinfin(safe.xinfin.org or sth):

safe.scroll.xyz
multisig.mantle.xyz
safe.coredao.org
safe.berachain.com
And so…

I would like to know everybody’s feedback on this post and feel free reshare to reach to a broader audience.

I’d appreciate it if the Oryy team resolved the above-listed questions.

Thanks for reading. Cheers.

2 Likes

i have same questions

2 Likes

I would like to know if it’s possible to open-source the contract code of the multisig wallet so that I can verify its reliability.

Additionally, I need a way to interact with the multisig contract directly, without going through the frontend.

2 Likes