Skip to content
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

Open
minhbsq opened this issue May 30, 2024 · 10 comments
Open

Register a private validium chain without publicly accessible RPC #5191

minhbsq opened this issue May 30, 2024 · 10 comments
Labels

Comments

@minhbsq
Copy link
Contributor

minhbsq commented May 30, 2024

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:

  1. Does this make sense to register it in the first place?
  2. If yes, can we leave the RPC endpoints as empty?

Thank you for your time in answering these questions

@ligi
Copy link
Member

ligi commented May 30, 2024

why does something like this even exist?

@minhbsq
Copy link
Contributor Author

minhbsq commented Jun 5, 2024

@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

@ligi
Copy link
Member

ligi commented Jun 5, 2024

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.

@ethereum-lists ethereum-lists deleted a comment Jun 5, 2024
@Sintayew4
Copy link

#5191

@tuanfish
Copy link

tuanfish commented Jul 8, 2024

0x93602868D7603097C56321599Ec0b65b91Cb7367

@minhbsq
Copy link
Contributor Author

minhbsq commented Jul 12, 2024

@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?

@nnlgsakib
Copy link
Contributor

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:

  1. Does this make sense to register it in the first place?
  2. If yes, can we leave the RPC endpoints as empty?

Thank you for your time in answering these questions

bro seriously?

@kennet31526
Copy link

kennet31526 commented Aug 28, 2024

It was stolen by krypton.so I don’t no what todo

@Mohmmaa
Copy link

Mohmmaa commented Oct 1, 2024

R

Copy link

This issue has no activity in a while - it will be closed soon.

@github-actions github-actions bot added the Stale label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

11 participants
@ligi @tuanfish @nnlgsakib @minhbsq @Sintayew4 @kennet31526 @Mohmmaa and others