Shane

Catch @Block_Shane tomorrow at EthCC. Shane will be on the Hepburn Stage at 15:25 - 15:45 (CEST), asking what it would look like if DVT infrastructure borrowed Ethereum's best habits. SIPs, specs, interop, client diversity and why that matters for trust-minimised, fault-tolerant staking.

ePBS breakout call 24 recap! Agenda: github.com/ethereum/pm/is… • New spec release v1.6.0-beta.0 with lots of ePBS updates. • Clients have containers + fork boilerplate implemented. • In 2 weeks we'll know if devnet-0 is possible by end of Oct. • Clients should create an epbs-devnet-0 branch for ethpandaops. • DataColumnSidecar may need a slot field (not a big concern). • Moving blob KZG commitments outside the block looks difficult. • ForkChoiceNode will be converted from a container to a dataclass. • The race to fully implement devnet-0 is on!

ePBS breakout call 23 recap! Agenda: github.com/ethereum/pm/is… • We will fix/merge a few spec PRs today. • Terence wants to us discuss fork-choice test case/scenarios. • We are still planning for devnet0 at the end of October! Will be a tough deadline though. Devnet0 will contain at least one client; Teku is currently the furthest along. • For the beacon state we have agreed to: keep latest_execution_payload_header as it is today, remove latest_block_hash field, and add new latest_execution_payload_bid field. • Alex Stokes and others want to refactor get_expected_withdrawals spec because it’s become quite complex/unwieldy. For devnet0, we agreed to keep the withdrawals code as it is now. • Shane lead a discussion on necessary beacon API changes for ePBS. Requesting more reviews from maintainers & client devs for his PR (github.com/ethereum/beaco…). We agree to make a V4 version of the GET /validator/blocks/{slot} endpoint. • Potuz learns that Jim McDonald retired :) • Bharath opened discussions on how eBPS will work existing out-of-protocol software like mev-boost. Potuz and some others lean towards not supporting this & only allowing payloads from in-protocol, staked builders. • Owen raised a good question about whether or not in-protocol builders will exist (and be able to submit payloads) at the first slot after the fork. This will require further investigation.

@Sui_Summit hi @Sui_Summit, I have been building in defi for 3 years now. Would love to join the summit and find some ways to contribute to the ecosystem. Sent a DM : )

If you’re a developer of any kind. Front end, backend, devops, etc. We have space for you. Dm us! We will get you in.

@dennis_inj inj1z6h0rrd65dqe2tc679u4edyevrmgmlhr48rl0w

I think I just created the first ai token on Injective using the new AI agent capabilities. rt and drop your addy so I distribute this historical piece 🤝

@OUT_Ninja1 @bangjelkoski @OUT_Ninja1, want to help, just looking for some more info to look into this. old bridge wont be up for much longer tbh

A completely new bridging experience for the Injective Ecosystem! 🌉🚀

@OUT_Ninja1 @bangjelkoski a screenshot of where in the flow the issue occurs could be helpful as well feel free to hide any info you dont want to share publicly, i.e. amounts/addresses

@bangjelkoski On the old bridge you approve INJ & then transfer. New bridge only allowed me to approve…it never gave me the option to transfer. I had to go back to the old bridge to transfer

@OUT_Ninja1 @bangjelkoski heyy @OUT_Ninja1, were you trying to withdraw or deposit? and by "approve", do you mean "set allowance"?

• What makes Injective different • Injective plug-and-play modules • Injective's interoperability (inEVM, inSVM) covered in an episode below by @Block_Shane from @injective

.@Block_Shane @EthereumDenver sahnasida Multi-VM muhitida qurish haqida suhbatlashdi 🏗️ #Ninja #INJ #Injective x.com/EthereumDenver…

@Block_Shane @injective x.com/EthereumDenver…

. @Block_Shane a urcat pe scenă la @EthereumDenver pentru a vorbi despre construirea într-un mediu Multi-VM 🏗️ x.com/EthereumDenver…

.@Injective_ is a Layer 1 blockchain that aims to democratize access to financial markets. How? By making it easy to to build & deploy apps across multiple chains like @Cosmos, @Ethereum, @Solana & more! Dive into the world of Injective: ledger.com/academy/what-i…

Basic blockchain knowledge: how does wallet apps derive your address from your seed phrase? This is a rather complex process, involving many steps, summarized in the diagram below: #1 --> #2 1st step is to convert your human-readable seed phrase aka mnemonic phrase (#1 in the diagram) into a raw binary seed (#2), aka entropy. The standardized algorithm for this conversion is Bitcoin Improvement Proposal (BIP)-39: github.com/bitcoin/bips/b…. Despite the "bitcoin" in the name, this standard is adopted by all other chains as well. #2 --> #3 Next we derive the private/public key pair (#3) from the seed. The algorithm for this is defined by BIP-32: github.com/bitcoin/bips/b… Here it gets a bit complicated. The BIP-32 algorithm takes 2 parameters: the seed, and another thing called the derivation path. The idea is that people may have multiple wallets for different purposes, but they probably don't want to keep record of many seed phrases. BIP-32 allows users to use only one seed, but combine it with various derivation paths to generate different wallet addresses. The specific format of derivation path is standardized by yet another BIP, BIP-44 (github.com/bitcoin/bips/b…). It looks like this: m / purpose' / coin_type' / account' / change / address_index The two fields that are worth mentioning are coin_type and address_index. The latter is easy to understand-- your first address uses index 0, the 2nd uses 1, so on. When you click "Add account" in MetaMask to generate a new address, what it does behind the scene is to increment the value of this address_index. coin_type is where it gets a bit controversial, at least within the Cosmos ecosystem. This parameter designates which chain the account is intended for. Satoshi Labs, the creator of Trezor wallet, maintains a registry called SLIP-0044 (github.com/satoshilabs/sl…) that allocates a number for each chain. Bitcoin gets coin_type 0, Litecoin gets 2, Dogecoin 3, Ethereum 60, so on. The controversial part is that deriving a different address for each chain may create problems for user experience. There has been a debate on whether all Cosmos chains should use the same coin_type, 118, that of Cosmos Hub. Another opinion is that Cosmos chains should just align with Ethereum and use 60. Let's not go too deep into the rabbit hole for now. #3 --> #4 Now we derive the address in its raw binary form (#4) from the public key. This is where it gets really messy. Unlike the previous steps which are well standardized, here each chain has its own methodology. To name a few: Bitcoin address := ripemd160(sha256(pubkey)) Ethereum address := keccak256(pubkey)[-20:] Cosmos address := sha256(sha256(typ) || pubkey) **1 Sui address := blake2b256(flag || pubkey) **2 Here sha256, ripemd160, keccak256, and blake2b256 are all cryptographic hash functions. **1 `typ` is a string designating the pubkey type. Typically the Protobuf typeURL is used. See: github.com/cosmos/cosmos-… **2 `flag` is a single byte that designates which ECDSA curve the account uses. See: docs.sui.io/concepts/crypt… #4 --> #5 Our address is now in its raw binary form, meaning a few hundred 0s and 1s. The final step is to encode it to a human-readable form. Here's another place where chains take different approaches. There're 3 encoding schemes used: - bech32: Bitcoin and Cosmos - hex: Ethereum, Aptos, Sui - base58: Solana What we should know is that the encoding schemes are just for the ease-of-use by humans. Blockchains operates on raw binaries and don't care how humans encode them. The very same address can look totally different when encoded in various schemes but its underlying bytes are unchanged. For example, this is the hex-encoded address for vitalik.eth: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 This is the very same address in Bech32 encoding: cosmos1mrdxhunfvjhe6lhdncp72dq46da2jcz9d9sh93 In base58: 42E5f5XLWJkBaQc3DdthcgUycdYQ Implementation I have a Rust code snippet for deriving the address (using Bitcoin's approach and bech32 encoding) for those who're interested: gist.github.com/larry0x/92399b… ------------------- That's it! Thanks for tuning in to my lecture. Let's summarize the nerd words you learned today so that you can show off to your friends: - BIP-32 - BIP-39 - BIP-44 - SLIP-0044 - coin_type - account_index - bech32 - base58 - hex

@gorgos The AI gods work in mysterious ways 🙇

The pitfalls from using AI for refactors. Took me quite a while to notice that ChatGPT had for no reason just decided to remove the amounts for these lines. Everything else was perfect code. And this one is so hard to notice when you're not expecting it.

.@Injective_'s order-book has done over $46M in volume in the last 24 hours. What many do not know... So many new markets coming to the CLOB soon, dozens of new dapps which will integrate the orderbook poised to deploy to mainnet in the coming quarter, illuminate hackathon w Google Cloud upon us The future is so damn bright

Me @olafriche and @BabakekereOfKP decided to give out society in what we receiving from @Injective_, as an act of charity and mode of offline promotion for #injectivel #blockchain Check trends for the full updates⤵️⤵️

Have you ever imagined you would be able to write one single command and immediately start building dApps on top of @Injective_? Whether it's a DEX, Smart Contract, or a fully customizable dApp, now it's a single command away! And we support both React and Vue (Nuxt) out of the box! 🔥🥷🏻 #create-injective-dapp-cli-tool" target="_blank" rel="nofollow noopener">docs.ts.injective.network/building-dapps…

🧵 3/7 We design mechanisms for privacy and infrastructure protocols which make them useful, valuable, and secure – the three principles of tokenomics.