-
Notifications
You must be signed in to change notification settings - Fork 73
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
Add opBNB (Binance Smart Chain L2) #1815
Comments
Hi @EthanBlockson we will be looking at additional QRNG deployments later in the year. Do you have a requirement for RNG on the network? |
opBNB will be main L2 of Binance Chain, so it will be perfect to have QRNG in onBNB, with the same config set as Arbitrum, or any other current EVM network. |
@KenCarvAPI any updates regarding where I can transfer this issue? Otherwise I'll close it because we're not taking RRP integration requests. |
Sharing a space in the ecosystem github that request can be directed to.
Also speaking with BNB team re potential deployment to opBNB for price so
could consider this actioned.
…On Thu, 10 Aug 2023 at 15:01, Burak Benligiray ***@***.***> wrote:
@KenCarvAPI <https://github.com/KenCarvAPI> any updates regarding where I
can transfer this issue? Otherwise I'll close it because we're not taking
RRP integration requests.
—
Reply to this email directly, view it on GitHub
<#1815 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUVEIKMH5HXNIH3UZKAYRMLXUTSTPANCNFSM6AAAAAAZSLCKAA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Seems to be done in #2000 |
Introducing opBNB: Unleashing a New Era of Scalability
Will Quintessence and QRNG providers will support opBNB?
The text was updated successfully, but these errors were encountered: