-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Register a private validium chain without publicly accessible RPC #5191
Comments
why does something like this even exist? |
@ligi The reason is that we operate under a trustless model, but not permissionless since we are building a regulated exchange and there are regulations that we need to follow regarding Anti Money Laundering. A permissionless model would mean that anyone could interact with our chain and bridge money in, which could violate our AML policy |
I am really torn here - on the one hand I strongly believe in permissionless blockchains - on the other hand I do not want chainIDs to collide to not open the door for replay attacks. |
0x93602868D7603097C56321599Ec0b65b91Cb7367 |
@ligi sorry I haven't replied sooner. I have the opinion that there shouldn't be a one size fit all model, and there's a spectrum between trustless - permissionless that can cater to the different use cases. Should this repo be open to that vision too? |
bro seriously? |
It was stolen by krypton.so I don’t no what todo |
R |
This issue has no activity in a while - it will be closed soon. |
I want to register a Layer 2 chain that is powered by ZkSync. The chain is a private Validium chain and the there's only one operator that can access the RPC server (ie: RPC is not open to public). All user operations needs to be proxied via the operator.
The point of registering this chain in is that we can make sure the user can sign the transaction with the right chainID. My questions are:
Thank you for your time in answering these questions
The text was updated successfully, but these errors were encountered: