Advanced articles

Bitcoin Optech #429 highlights a proposed way for multiple signers to construct Silent Payments and verify their contributions. The design remains research, with an important security assumption unresolved.

Circle’s CCTP article describes connections for non-USDC tokens. Issuer-controlled and ownerless configurations have different control arrangements, so not every route should be understood as the same burn-and-mint process.

Lichen is a research design for a single-issuer layer 2 that aims to let users recover bitcoin through an onchain dispute process when the issuer will not cooperate. Users and the issuer lock funds separately, with redemption rights subject to an agreed capacity. Tokens above that limit still require the issuer's cooperation.

The design continues to depend on the sequencer recording state correctly; malicious sequencing can cause losses. The newsletter also covers a proposal to store known hash preimages in output descriptors. These secrets should be backed up and protected like keys, and excluded from public descriptors.

The Ethereum Foundation postponed Hoodi's Glamsterdam upgrade, previously scheduled for October 26, to investigate interactions between EIP-8037 and mainnet smart contracts. The scheduled execution-layer and consensus-layer upgrades and gas-limit increase were removed together. At the time of this review, the announcement provided no replacement activation date.

This removes a future upgrade configuration rather than reverting chain history. Hoodi operators need to follow updated client instructions instead of assuming versions in the older announcement include the postponement. The notice concerns the testnet and does not set a mainnet activation date.

This issue introduces a draft allowing peers to assign their own one-byte message identifiers for BIP324 transport. Aliases announced when connecting could reduce dependence on a globally coordinated table for new messages. The proposal concerns network transport and is not an already activated consensus change.

It also covers Shielded Bitcoin, which explores hiding transfer amounts and counterparties through encrypted notes, nullifiers and external verification. Details of its deposit and exit mechanisms were awaiting a companion paper. The design remains research rather than a completed privacy product.

zkAPI lets users deposit credits into an Ethereum contract and authorize API spending with zero-knowledge proofs. A server can verify sufficient funds and prevent double spending without learning which deposit paid. Short-lived API keys cap spending, with sessions settled according to actual usage.

The design primarily hides the link between payment and usage. It does not automatically conceal request contents or network information: providers still see prompts, and IP addresses, timing and repeated content may reveal connections. Proxy mode also exposes traffic to the intermediary.

Ethereum layer-2 networks aim to handle more activity outside the mainnet while using its settlement or data capabilities. Rollups, for example, execute transactions on another layer and submit relevant data or results to Ethereum, spreading costs across multiple operations. This helps explain why L2 networks can offer lower fees.

L2 is not a single product: networks differ in technology, smart contracts and maturity. The source notes that networks claiming to scale Ethereum do not necessarily use the same security model, and there is no single official L2.

Ethereum staking uses ETH to support validators that help confirm blocks and receive participation rewards. Activating an independent validator requires at least 32 ETH and involves equipment and connectivity requirements. Delegated operation and pooled staking offer other routes, but distribute control and responsibility differently.

The source compares solo staking, delegated services, liquid staking and pools. Lower capital or technical requirements often come with additional dependence on third-party operators, contracts or custodians.