Vivant Reliquiae #96900 Hand-painted oil metallic & acrylic on 24 x 48” 6mm thick honeycomb-core ACM panels, frame in black ash hardwood, faced with Optium museum acrylic on 1/4” spacers DM for custom work ⚡️

Vivant Reliquiae #96900 Hand-painted original Photos and edit coming soon…

We Are All Satoshi 20 × 20 × 1.5 in, Oil based metallic, acrylic, hand-painted original, hand-stretched on cotton canvas Includes a signed @npub1yjry...33a9 vintage card with the same art 👀 Bid Now at

CLCT

Asanoha — We Are All Satoshi · CLCT

The kanji says, “Satoshi”. In Japanese, the first character represents, “wise, sage, philosopher”. The second character represents, “hist...

On display at MWBTCSummit The kanji says, “Satoshi”. In Japanese, the first character represents, “wise, sage, philosopher”. The second character represents, “history, chronicle”. The 8-bit style font is a nod to cypherpunks and gamers, the first people to adopt bitcoin. A bit is the smallest unit of data that a computer processes. A bit is always in one of two physical states, represented as a binary value, usually a 1 or 0. The state it is in may also be represented as on/off, yes/no or true/false. Pixels on a display monitor are made of bytes. A black & white pixel contains one byte, a 24 bit RGB color pixel contains three bytes. There are 8 bits in one byte. The more bits in a monitor that are turned on, the more processing power that is required, which was very limited back in the day. The 8-bit font’s letters and numbers were a tactile balance of conserving computer memory. Old arcade games looked the way they did because they were an exercise in efficiency. Thanks to Bitcoin, we now have the most proficient financial system to have ever existed. A chance to regain our sovereignty from the tyranny of the centralized banking cartel. The aphorism, “We are all Satoshi” has been shared since the early days of Bitcoin. It has been over ten years now that the creator himself left us. To this day no one knows who he was, but perhaps there is a little bit of him in each of us. Handpainted original. Hand-stretched on gallery bars.

Grateful to everyone who has dropped a bid so far on my painting This is an extraordinary, rare and exotic opportunity to own an original Asanoha 100% of the proceeds from this sale will go towards printing Edition One of Timechain magazine ⚡️ Big ups to @npub129de...ngjc for curating the gallery

Bidding is live 🔥 We Are All Satoshi Hand painted original

CLCT

Asanoha — We Are All Satoshi · CLCT

The kanji says, “Satoshi”. In Japanese, the first character represents, “wise, sage, philosopher”. The second character represents, “hist...

Is it just me or is Damus so slow it’s basically unusable?

The Genesis Edition Ft. @Anik Malcolm @npub1s2xr...g4c9 @npub1yjry...33a9 @npub1lceh...pa0l @Bitko Music: Emapea

In auction now 🔥 We Are All Satoshi 20 x 20” hand painted original The kanji says, “Satoshi”. In Japanese, the first character represents, “wise, sage, philosopher”. The second character represents, “history, chronicle”. The 8-bit style font is a nod to cypherpunks and gamers, the first people to adopt bitcoin. A bit is the smallest unit of data that a computer processes. A bit is always in one of two physical states, represented as a binary value, usually a 1 or 0. The state it is in may also be represented as on/off, yes/no or true/false. Pixels on a display monitor are made of bytes. A black & white pixel contains one byte, a 24 bit RGB color pixel contains three bytes. There are 8 bits in one byte. The more bits in a monitor that are turned on, the more processing power that is required, which was very limited back in the day. The 8-bit font’s letters and numbers were a tactile balance of conserving computer memory. Old arcade games looked the way they did because they were an exercise in efficiency. Thanks to Bitcoin, we now have the most proficient financial system to have ever existed. A chance to regain our sovereignty from the tyranny of the centralized banking cartel. The aphorism, “We are all Satoshi” has been shared since the early days of Bitcoin. It has been over ten years now that the creator himself left us. To this day no one knows who he was, but perhaps there is a little bit of him in each of us. Handpainted original. Hand-stretched on gallery bars. Bid now here:

CLCT

Asanoha — We Are All Satoshi · CLCT

The kanji says, “Satoshi”. In Japanese, the first character represents, “wise, sage, philosopher”. The second character represents, “hist...

Love it 😍🔥 View quoted note →

The Weekly Canvas featuring BTC Monk, Tructor & @Anik Malcolm just dropped ⚡️ Hesitant to sign up to another newsletter? Take a look below at the simple & clean high signal content we are pushing, our goal is a newsletter you actually want to read 🤌🏽 Sign up in the bio of @Timechain Art Magazine https://timechainartmagazine.com/signup

Have you signed up to the Bitcoin Art Newsletter from @Timechain Art Magazine? https://timechainartmagazine.com/signup

S19 Pro 110Th/s ⚡️ On display and in auction at The Space Denver >>> Bid Now at @npub1rujw...00fg <<< Limited Edition of 100. - 12” x 16” Fine art archival serigraph, metallic gold ink, archival paper stock. - Signed and numbered. - Framed with anti-glare acrylic. In February 2020, Bitmain released the Antminer S19 Pro, one of the most powerful sovereignty securing machines ever created. With a hashrate of 110TH/s + 3%, and a power consumption of 3250W + 5%, it has an efficiency of 29.5±%5 J/TH, making the S19 Pro one of the most efficient bitcoin mining machines ever made at the time.

I need help debugging! Can you please go on the @Timechain Art Magazine website and scroll to the bottom of the homepage and tell me if the sponsor ticket is working for you?

Support your local artists. Order a magazine. @Timechain Art Magazine https://bitcoinartmagazine.com

Where is the best place to create a nostr follow pack?

Are you here for the separation of money and state anon? View quoted note →

There’s a lot of people who need to remember that Satoshi created Bitcoin to separate money from state. He very clearly said so in his first public announcement introducing the Bitcoin software after releasing the whitepaper in October 2008 and the genesis block in January 2009. In a February 11, 2009 post on the P2P Foundation forum announcing the Bitcoin software, Satoshi wrote: “The root problem with conventional currency is all the trust that’s required to make it work. The central bank must be trusted not to debase the currency, but the history of fiat currencies is full of breaches of that trust. Banks must be trusted to hold our money and transfer it electronically, but they lend it out in waves of credit bubbles with barely a fraction in reserve. We have to trust them with our privacy, trust them not to let identity thieves drain our accounts. Their massive overhead costs make micropayments impossible.”

Satoshi Nakamoto Institute

Bitcoin open source implementation of P2P currency | Satoshi Nakamoto Institute

I've developed a new open source P2P e-cash system called Bitcoin. It's completely decentralized, with no central server or trusted parties, becaus...

Very clear breakdown by @npub1cjw4...j2rh of why Knots adoption is growing so fast: 1/ In 2025 Bitcoin Core removed a decade-old mempool policy default — a configurable limit on how much non-financial data nodes would relay. OP_RETURN was effectively uncapped. Not a consensus rule. A default setting. But defaults govern what most of the network does. Which governs what miners see. Which governs what gets mined. The justification: it wasn’t working anyway, data was getting in through a loophole. What wasn’t disclosed: that loophole had been deliberately kept open. Here’s the documented sequence. 🧵 2/ 2014: Luke Dashjr creates the -datacarriersize configuration option. Its description: "Maximum size of data in data carrier transactions we relay and mine." Broad by design. Covers all transaction components. That's the operative text for ~10 years. 3/ Late 2023: Developer Marco Falke changes the -datacarriersize description in v26.0. New wording inserts "scriptPubKey" — outputs only. Inscriptions use the input/witness section. That single word change surgically excluded inscription spam from the option's scope. Image 4/ That change was not a typo fix. AJ Towns ACKed it. The diff is documented. The before/after screenshot exists. The configuration option Luke built to protect the network had its scope quietly narrowed — while he was still maintaining the project. 5/ Sept 2023: Luke submits PR #28408. Purpose: extend -datacarriersize to cover the SegWit/Taproot witness loophole inscriptions were using to bypass existing limits. A direct fix. Using the exact configuration option he built. Nine years earlier. 6/ Gloria Zhao rejects it. On-record comment: "History of this config option suggests datacarriersize is meant to limit the size of data in OP_RETURN outputs, so this statement is untrue." She cites curated historical PRs to support the narrowed reading. 7/ She does not mention that the operative description in the codebase had been changed in v26.0 by Marco Falke. AJ Towns — who ACKed that documentation change — then gives an Approach NACK on Luke's patch. The same man enabled the rejection and then ratified it. 8/ Peter Todd also NACKs. Calls Luke's patch "censoring" transactions. He does not disclose he operates Libre Relay — a direct-to-miner relay that routes inscription transactions around mempool policy. He built the bypass. Then called closing it censorship. 9/ PR #28408 closes. 11 Concept NACKs vs 9 Concept ACKs. The loophole remains open. Jan 5, 2024: Luke opens Issue #29187 and formally designates the bypass as a security vulnerability: CVE-2023-50428. "Active exploitation... very harmful to Bitcoin even today." 10/ Oct 2024: Contributor darosior disputes the CVE. "The large majority of contributors disagree this is a security vulnerability. I believe the CVE system is being abused." Next day, achow101 closes the issue. The vulnerability is officially declared not a vulnerability. 11/ April 2025: Peter Todd files PR #32359 to remove the OP_RETURN limit entirely. He later admits: "This pull-req wasn't my idea. I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs instead of OP_Return." 12/ Citrea: a VC-funded ZK-rollup whose business model needed more on-chain data storage. Jameson Lopp publicly advocates for the PR. He is an investor in Citrea. This was not disclosed. 13/ Samson Mow calls it "PR laundering" — routing through Todd to fake independent initiative. Antoine Poinsot (Chaincode Labs) connected to early discussions. The same Poinsot who disputed Luke's CVE in October 2024. He sits at both ends of the sequence. 14/ June 9, 2025: Gloria Zhao merges the uncapped OP_RETURN change. The primary public justification: inscription data via the witness loophole is less prunable, so OP_RETURN should be uncapped to redirect it. The harm reduction argument. 15/ That argument is entirely dependent on the witness loophole remaining open. If PR #28408 had been merged in 2023, the loophole would be closed. The harm reduction argument would not exist. It would have had nothing to reduce harm from. 16/ The person who rejected the patch that would have closed the loophole is the same person who merged the change that used the open loophole as its justification. That is not a coincidence. That is a sequence. 17/ The last entry in Luke's closed CVE issue reads: "glozow mentioned this on Jun 9, 2025 — policy: uncap datacarrier by default #32406" The issue opened to fix the vulnerability referenced from the PR that exploited the unfixed vulnerability. GitHub closes the loop. 18/ Every step is documented: → Docs narrowed (v26.0, ACK: Towns) → Patch rejected using narrowed docs (Zhao, Chow) → CVE designated (Luke, Jan 2024) → CVE closed (darosior, achow101, Oct 2024) → Removal PR commissioned (Todd) → Uncap merged (Zhao, Jun 9 2025) 19/ Adam Back claimed the narrowed definition "was always the original intent." The original 2014 text has no mention of OP_RETURN, scriptPubKey, or outputs. That restriction was introduced in v26.0. He treated an amendment as original intent. 20/ The PR had 423 thumbs-down against 105 thumbs-up. Ava Chow had said publicly in Dec 2023: "If it is controversial, then we don't touch it." It was merged anyway. Luke Dashjr was muted on the PR. Bitcoin Mechanic was muted on the PR. 21/ Bitcoin Core's response: → 31 devs sign a letter calling opposition "censorship" → GitHub moderators mute the loudest critics And: → Nick Szabo breaks 5-year silence: "run Knots" → 22% of the network switches to alternative software 22/ The documentation was rewritten. The patch was rejected using the rewrite. The loophole was kept open. The open loophole became the justification. The justification enabled the uncap. The person who rejected the patch merged the uncap. All on the public record. /end

Illuminati is recruiting on nostr lol