On the _everyone is scammer_ front: Somehow I feel its better to earn (_scam_?) fiat from normies, than bicoin from the bitcoiners Work it fiat, save in bitcoin

Wen do the bond markets open? r u ready?

Purpose 45 Multi-party P2SH multisig wallets (m-of-n) m / 45′ / cosigner_index / change / address_index Multiple independent users each have their own master key. They share only their hardened purpose public key so any cosigner can derive the full set of pubkeys for a shared multisig address without talking to the others.

Candle broke Cashapp

@Bluewallet absolute fire.... Whats my derv path? didnt save it... F-ed Imported seed for hot wallet to sweep a modest stack, when you type in custom paths it scans realtime for UTXOs + highlights button. Only took me 3-4 iterations to find UTXO - amazing

Running core 29.3 Holding my own keys Working to avoid force selling Hoarding without permission Will spend my corn later for my future self, again without permission

41 trillion incoming. Ignore the noise. One money wins. "When Does the Debt Ceiling Need to Be Renewed? According to projections from the Bipartisan Policy Center (BPC) and the Committee for a Responsible Federal Budget (CRFB), the U.S. is expected to officially hit this $41.1 trillion limit sometime between late winter and mid-summer of 2027. However, the exact timeline unfolds in two distinct phases: Phase 1: Reaching the Limit (Early-to-Mid 2027): Once the $41.1 trillion cap is breached, the Treasury Department will no longer be allowed to issue new net debt. To keep paying the nation's bills, the Treasury will deploy accounting maneuvers known as "extraordinary measures" while drawing down its cash reserves. Phase 2: The "X-Date" Deadline (Late 2027): These extraordinary cash-management tools are expected to buy Congress an additional six to nine months. Once those reserves are entirely exhausted, the U.S. will hit its hard "X-Date"—the absolute deadline by which Congress must pass legislation to raise or suspend the cap to prevent an unprecedented federal default. Because the stopgap spending bill passed by the Senate only funds government operations through December 11, 2026, lawmakers will face a massive budget showdown at the end of 2026. However, they will still have a multi-month cushion into 2027 before the separate debt ceiling mechanism forces a high-stakes legislative renewal.

Over the real numbers, **y² = x³ + 7** looks like a single smooth curve with **two branches** (upper and lower) that are mirror images across the x-axis. - **One connected piece**: Unlike some elliptic curves that form a separate closed loop plus a tail, this one has just a single open curve because x³ + 7 has only one real root (at x = –∛7 ≈ –1.91). - **Leftmost point**: The curve meets the x-axis at roughly (–1.91, 0) with a **vertical tangent**, creating a rounded “nose” or “toe” on the left. - **Extending rightward**: From that point, the curve splits into an upper branch that curves upward and a lower branch that curves downward. Both stretch out to infinity toward the right, growing steeper as x increases. - **Symmetry**: Because of the y² term, everything is perfectly symmetric across the x-axis. **What “smooth with no singularities” means:** - **No self-intersections** (unlike a figure-eight or lemniscate) - **No cusps** or sharp corners - **No isolated points** The curve is continuously differentiable everywhere. If you zoom in at any point, it looks like a gently bending line. The “smooth” part is exactly what makes the geometric addition law work in elliptic curve cryptography: you can draw a line through any two points and it will intersect the curve cleanly in exactly one more point.

Private keys: ✅Yes, use sufficient entropy when creating them ✅Yes, minimize trust when protecting them ✅But, also protect them when you're signing to spend Offline, analog as much as possible

PBKDF2 is a form of hash function that is designed to be slow (by hashing the data multiple times before producing the result). This has the benefit of making it more difficult for anyone to brute-force mnemonic sentences to try and get seeds that people have actually used. In addition, PBKDF2 also allows you to provide a second input called a salt ("passphrase", "seed extension") along with the data you want to hash, which allows you to produce completely different seeds from the same mnemonic sentence. - learnmeabitcoin.com

Not sure is this logic holds but, hit me back if I'm way off: - rolled my own entropy + pass phrase; 2-4 years later key not swept, likely means I'm good _forever_? as if the entropy was bad, then the money would have been gone long ago vs - use hardware _X_ to generate key; 2-4 years later, still not safe as AI+wizard humans could still hack/uncover weak spot in the hardware down the road (=AGI future)

Dont forget the USD is the real shitshow. Stealing from everyone forever.

Long 48 hours of redoing some private key generation, dice rolls, remembering set ups, triple checking, testing back ups. Silver lining: was mostly ready. Sparrow fire. Good practice doing this. Also, wife, fully engaged, asking tons of questions.

The focus on Fed rate is pure noise. Short-term rates mean nothing. Real rate is determined by the market (=10+yr bond sales). When appetite is low for US 10y they MUST raise the rate to attract more suckers (=buyers). When market tells them _no thanks_, they will just buy debt themselves = yield curve control = fiscal dominance = ponzi Opt out.

BIP 110 contentious debate is a nothing-burger compared to what could be coming...... Wait til governments and large corporations are disagreeing about bitcoin + censoring each other. It will always be work/physical energy that resolves conflict. Gold was a physical, bearer asset. I have the Gold, I make the rules until someone takes it from me. In Bitcoin real physical energy also resolves the conflict. Economic nodes. Hashers. Out-of-bound transactions: real work, in the real world. The way to transact in a future hostile world will be: run an economic node, build blk-templates yourself, harness energy, hash. Always without permission. Always with real work.

The Historical Reason Electrum Servers Exist When the Electrum wallet was created in 2011, Bitcoin Core could not serve light clients. The Electrum protocol was invented specifically to decouple the wallet from the node: Bitcoin Core stays in charge of consensus and the P2P network. Electrum Server traverses Core’s data and builds a fast, queryable address database. Electrum Wallet (or Sparrow, BlueWallet, etc.) connects to the server and downloads only the tiny slice of data relevant to the user’s keys. This architecture let phones and laptops run wallets without downloading 600 GB of blockchain. The Modern Alternative (Block Filters) There is a newer way to achieve a similar goal without trusting a specific Electrum server: BIP 158 compact block filters (client-side filtering / Neutrino). Bitcoin Core can build a filter index (blockfilterindex=1). Instead of asking a server “what is my history?”, the light client downloads a small, compressed filter for each block and checks if any of its addresses might appear in that block. If the filter matches, the client fetches the full block (or relevant transaction) from the node. This is more private (the server doesn’t learn your addresses) but still requires more bandwidth and CPU on the client than the Electrum protocol. Because compact block filters are relatively heavy for small devices, the Electrum protocol remains the dominant method for desktop and mobile wallets. Bottom Line You need both: Core’s RPC to run the node, validate the chain, and broadcast transactions. An Electrum server to let light wallets query the chain by address quickly. One provides the raw truth; the other provides a fast lookup layer on top of it.

The Historical Reason Electrum Servers Exist When the Electrum wallet was created in 2011, Bitcoin Core could not serve light clients. The Electrum protocol was invented specifically to decouple the wallet from the node: Bitcoin Core stays in charge of consensus and the P2P network. Electrum Server traverses Core’s data and builds a fast, queryable address database. Electrum Wallet (or Sparrow, BlueWallet, etc.) connects to the server and downloads only the tiny slice of data relevant to the user’s keys. This architecture let phones and laptops run wallets without downloading 600 GB of blockchain. The Modern Alternative (Block Filters) There is a newer way to achieve a similar goal without trusting a specific Electrum server: BIP 158 compact block filters (client-side filtering / Neutrino). Bitcoin Core can build a filter index (blockfilterindex=1). Instead of asking a server “what is my history?”, the light client downloads a small, compressed filter for each block and checks if any of its addresses might appear in that block. If the filter matches, the client fetches the full block (or relevant transaction) from the node. This is more private (the server doesn’t learn your addresses) but still requires more bandwidth and CPU on the client than the Electrum protocol. Because compact block filters are relatively heavy for small devices, the Electrum protocol remains the dominant method for desktop and mobile wallets. Bottom Line You need both: Core’s RPC to run the node, validate the chain, and broadcast transactions. An Electrum server to let light wallets query the chain by address quickly. One provides the raw truth; the other provides a fast lookup layer on top of it.

Maple AI: A server exposes an RPC (Remote Procedure Call) interface so other programs can talk to it programmatically. Think of it as the server’s control panel: instead of a human clicking buttons, another piece of software sends a command and gets a response. Here is why that is necessary, especially for something like a Bitcoin node. 1. The Daemon Is Headless Servers like bitcoind run in the background with no window, menu, or buttons. RPC is the only way to ask it questions or give it orders while it is running. Without RPC, the process would just sit there peer-to-peer syncing blocks, and you would have no way to query balances, send transactions, or check sync status. 2. Separation of Concerns The node’s main job is to validate blocks and stay in sync with the P2P network. Wallet logic, user interfaces, and business applications are built on top of the node, not inside it. RPC lets those external tools live in separate processes—or even on separate machines—while still commanding the node. Examples of what uses RPC: bitcoin-cli (the built-in command-line tool is just an RPC client) Wallets (Sparrow, Specter, BlueWallet, Electrum servers) Lightning nodes (LND, Core Lightning need to query on-chain state and broadcast transactions) Payment processors (BTCPay Server asks the node to verify payments) Scripts and bots (automated sweeping, balance checks, alerts) 3. The Two Ports Do Different Things Bitcoin Core listens on two separate networks: Port 8333 (P2P): Speaks the Bitcoin peer protocol. This is node-to-node traffic—gossiping blocks and transactions across the internet. Port 8332 (RPC): Speaks JSON-RPC. This is client-to-node traffic—your applications asking your node for private data or actions. If you only had the P2P port, you could relay blocks, but you could never ask your own node “what is my wallet balance?” or “send this transaction.” RPC is the query and control layer. 4. Service Integration In a stack like Start9, the Bitcoin node is one container and the other services (indexers, Lightning, explorers) are separate containers. They communicate via RPC. The indexer does not need to know how to validate blocks; it just asks Bitcoin Core via RPC for block data and transaction details. Why RPC Is Locked Down Because RPC is so powerful—it can move funds, dump private keys (in legacy wallet setups), and shut down the node—it is localhost-only by default and requires a username/password or cookie file. Opening RPC to the internet without a proxy, VPN, or Tor tunnel is dangerous, which is why setups like Start9 wrap it behind reverse proxies and authentication layers. In short: RPC turns a silent background process into a programmable server. Without it, the node could talk to the Bitcoin network, but nothing else could talk to the node.

2019–2024 — BIP 324 and Opportunistic Encryption The breakthrough came with BIP 324 (originally drafted by Schnelli in 2019, later revived and expanded by Dhruv Mehta, Tim Ruffing, and Pieter Wuille). What it does: It introduces a “v2” transport protocol that uses unauthenticated, opportunistic encryption over clearnet. Why it matters: It uses ElligatorSwift encoding to make the entire byte stream—including the handshake—indistinguishable from random noise. Passive surveillance can no longer identify Bitcoin traffic just by looking at packet headers. Timeline: Merged into Bitcoin Core in 2023 (v26.0) and enabled by default in v27.0 (2024). For the first time in Bitcoin’s history, the majority of clearnet P2P traffic is encrypted.