hidan

some anon playing best naruto hero

[hidan @hidan_eth]

@gmoneyNFT Some codes!:

https://t.co/gKoPxxN1Yr
https://t.co/DwCEjPStdI
https://t.co/4jCHoaQQvT
https://t.co/qVEMk9tJ12
https://t.co/pKxDRXdKVf

[hidan @hidan_eth]

Just scored xxxx Rabby Points with a few clicks, and got extra 250 points for migrating my MetaMask wallet into Rabby!

Everyone can get points, and use my referral code 'RABBYFERRAL' for an extra bonus.

Ready to claim? @Rabby_io

https://t.co/rjK4hIXy4Y

[hidan @hidan_eth]

@Pickle_cRypto hey mate, when official sei bridge fails in giving you $sei dust to transact, how/where can I get some?

to few bridges and I don't want to use CEX bc my addy isn't doxxed
thnks!

[hidan @hidan_eth]

Finally!! A bridge that has a "gas" section!
Congrats @jumperapp !!!

[hidan @hidan_eth]

ok, i'll bite:
#seinetwork best influencers?
#sei best meme tokens?

[ALEX | ZK @gluk64]

ZK proofs enable low-latency, trustless, zero-overhead bridging between permissionless and sovereign ZK chains with mixed data availability models. We call it hyperbridging. Not necessarily atomic, but seamless: one single confirmation in Metamask will let you interact with any smart contract on any other L2 in the ZK network, sending the result back to your wallet, in seconds.

This is a prerequisite for limitless scalability on Ethereum, and will solidify it as the global settlement layer of the Internet of Value.

Let's break it down:

- Low-latency. With sufficient parallelization, we can bring down the proof generation time for a block to seconds. The actual latency will be determined by the users preference for finality guarantees (either Ethereum will embrace single-slot finality, or chains will rely on economic finality guarantees), but it will be low in any case (seconds). But even if you insist on waiting to reach full finality on L1 under today's model, all the other benefits hold and are not possible with anything but ZK rollups.

- Trustless. Every user verifies the validity of all of the transactions on all chains and all the bridging transactions by relying purely on math. You never need to trust any validator, watcher, relayer—anyone else but yourself.

- Zero-overhead. With state diff architectures (uniquely enabled by ZK rollups and currently embraced by zkSync and Starknet), a bridging tx will cost nearly as much as a normal tx on either chains; if the chains have different costs, e.g. because one account is a rollup and the other one is a validium, total_cost = tx_cost(chain A)/2 + tx_cost(chain B)/2. This is because data availability is our main cost driver, and with state diffs you only pay for the storage slots you update where you update them.

- Permissionless, sovereign ZK chains. Ethereum is so powerful because anyone can deploy a smart contract. You don't have to ask Vitalik for permission or sign a contract with the Ethereum Foundation. To reach hyperscale, the same must be true for deploying L2s, an unlimited number of them. But that means most other L2s cannot be trusted, by default. No one has the capacity to verify all the value transactions of the world. Thus, most bridging must rely on fully trustless mechanisms. Using ZK proofs, it's easy. A single proof on L1 can attest to the validity of all the thousands of ZK rollups—and, what's very important, validiums (which will be responsible for the bulk of all transactions thanks to much lower costs). For optimistic rollups, you either have to wait 7 days, or you must explicitly whitelist a small number of shared sequenced rollups, which kills the ability to deploy L2s permissionlessly.

- Mixed data availability (DA) models. Rollups will always be relatively expensive, by design (because, unlike sidechains and alt L1s, they trustless prioritize security and censorship-resistance). Most L2s will thus have to use alternative DA layers which are much cheaper. The beauty of validiums and volitions (such as zkSync’s zkPorter) is that this affects neither verifiability nor bridgeability at zero overhead. The same does not hold true for optimistic rollups, though. There is simply no way to trustlessly bridge between an optimistic rollup and an Anytrust chain (such as Arbitrum Nova), even with a shared sequencer: by mixing optimistic DA models, or you will automatically downgrade all the optimistic rollups in this shared sequencing scheme to the least secure of them, rendering them not much more secure than a sidechain.

Nothing has changed about these fundamentals. Ethereum will win not even because of its first-mover advantage, but because its ethos and culture is focusing us on solving the right problems. What I describe above gives you infinite scalability – not 10k, not 100k, but arbitrary many TPS and users – while not sacrificing UX, decentralization, trustlessness, or resilience in front of mighty adversaries.

Have just a little patience, you will soon see all of it in action. I promise. 🍿

[cygaar @0xCygaar]

Summary of the Arbitrum outage and high Ethereum gas prices:

- People are spamming inscription transactions on Arbitrum. These are transactions that submit some hex data on-chain (images and metadata mostly).

- My guess is this overwhelmed the sequencer itself, preventing L2 txns from being executed.

- Arbitrum One is an Ethereum rollup so it posts compressed txn data back to Ethereum mainnet.

- Since there were so many inscription txns, the Arbitrum poster had to post many batches of calldata back to L1. We're talking somewhere in upper-5/lower-6 digit range.

- In general, the more txns on L1 in a given period, the higher the gas prices go (EIP1559 pricing). There are currently thousands of pending txns from the Arbitrum batch poster waiting to be executed.

- Since the gas prices increased, the Arbitrum poster had to resubmit many of its txns with higher gas prices.

I'm still monitoring the situation, so I'll post again when I find out more.

[hidan @hidan_eth]

@koeppelmann @LefterisJP 1. ordinals aren't in btc only?
2. $arb doesn't have fss from $link to order txs?
are they going to replay everything in orden? they will skip all txs? re-order them again?

What's have done solana each time broke down?

[hidan @hidan_eth]

@arbitrum processing transactions again

How would you replay everything?
Do you have FSS so it will be in correct sequence?

$ARB

[The Grinch That Tried To Warn You @1ng1n33r_]

@GMX_IO GMX V2 seems to be having a moment.

[hidan @hidan_eth]

@6245V @info_insightful @Rabby_io @MetaMask this post aged wrongly
appparently rabby not working today

[hidan @hidan_eth]

@Junko__Suzuki luckily staked $link need a cooldown period 😉

[hidan @hidan_eth]

@ErikBartos1 @Rabby_io Changed RPC and nothing

[Melex @iam_melex]

Can someone help me with this ?
Arbitrum network, can't make any sign or swap.
@Rabby_io any update for that ?

[hidan @hidan_eth]

ok, @Rabby_io not working for me

[hidan @hidan_eth]

$ETH is not going to happen this year folks!
Maybe next one, maybe never...

Everybody waiting for $ETHBTC to break out and thats why its not going to happen...

18224c483669fe910f434a216d8b425e25988e48c851bd9fb9d16e8080745077

[N̴̡̩̠̻̩͜͝a̴͍͙̫̹̅u̶̼̠̭͐̂͘h̷͇̻̭̚c̴͉͈̎̂̅͗̉̈́̆͑̍̀ @nauhcner]

By the way, props to @Rabby_io as the wallet did actually display a simulated transaction with the draining occurring (failed to take a screenshot), which should make you think something is wrong even if you weren't aware of the attack.
Even if Rabby also uses a lot of packages and is potentially vulnerable to the same type of supply chain attack, at least the wallet simulates the transaction before making you sign it.
There is really NO REASON to use metamask in crypto in 2023.

[Rabby Wallet @Rabby_io]

PSA: Please rest assured that Rabby Wallet is NOT affected by this attack.

We strongly advise users to avoid interacting with potentially affected Dapps.

Please check your signing page details carefully with Rabby Wallet, to avoid unexpected losses.

For more details about the attack: https://t.co/rdx4OY5mYR

[ً @lightclients]

ARG

[hidan @hidan_eth]

@zachxbt wow you are a fucking genius