Pinned Tweet
AD
NPM INSTALL
NPM RUN DEV
THE PROOFOFWORK COMPUTER CONTINUES.
github.com/proofofworkme/…
$WORK $INCB $POWB
0
3
6
1,754
IT SEEMS AS IF CODEX AND OPENAI HAVE COMPLETELY BRICKED WALLET EXTENTIONS
NPM INSTALL
NPM RUN DEV
THE PROOFOFWORK COMPUTER CONTINUES.
github.com/proofofworkme/…
$WORK $INCB $POWB
0
0
0
21
Pages, Code, Jobs and Permission now use the shared UniSat connection flow across ProofOfWork.Me.
Inside Computer, all four use Computer’s wallet session. Signing stays local.
computer.proofofwork.me
$WORK $POWB $INCB
Inside Computer, all four use Computer’s wallet session. Signing stays local.
computer.proofofwork.me
$WORK $POWB $INCB
0
0
0
12
The ProofOfWork Computer has its own on-chain metaprotocol stack.
Mail. Files. Identity. Domains. Credits. Social. Publishing. Code. Jobs. Permissions. Markets.
Here’s the protocol map and the actions inside it:
MAIL + FILES — pwm1:
• s = subject
• m = message body
• r = reply reference
• a = file attachment, verified by size and hash
Messages, documents, images and HTML become transaction-addressed records.
PROOFOFWORK IDs — pwid1:
• r2 = register
• u = update receiver
• t = transfer ownership
• list5 / seal5 / delist5 / buy5 = trade IDs
Ownership and message delivery are separate. Names are assets.
PROOFOFWORK DNS — pwdns1:
• r1 = register a .pow name
• u = update resolver
• t = transfer ownership
• list5 / seal5 / delist5 / buy5 = trade names
• sub1 → create / update / revoke a subdomain
• page1 → set / clear a root page link
• subpage1 → set / clear a subdomain page link
The confirmed owner controls the namespace.
CREDITS + WORK — pwt1:
• create = define a credit
• mint = mint credit
• send = generic whole-credit transfer
• send3 = WORK transfer with 16-decimal precision
• batch1 = standalone WORK transfer to 2–256 recipients
• mailbatch1 = WORK attachments for 1–256 ordinary Mail recipients
• list5 / seal5 / delist5 / buy5 = trade credits
Each WORK batch pays one 546-proof WORK registry fee. Mail delivery payments remain separate.
BOOST — pwb1:
• profile / post / reply
• like / reboost
• follow / unfollow
• tip = send proofs
• tip2 = send WORK
• hide = hide content from default views while preserving its history
• t = transfer content ownership
• list5 / seal5 / delist5 / buy5 = trade content
Quote posts reference another post inside the post record. Profiles and media reference verified Files.
PUBLISH
Articles combine pwb1:post metadata with exact pwm1:m article text.
Publish shares Boost’s profiles, engagement, tips and content ownership. The article’s words are bound to their on-chain record.
CODE — pwc1:
• repo = create a repository
• commit → put / delete a file
• commit2 → reference an existing confirmed Page
Exact source. Confirmed history. Repositories humans and agents can inspect.
JOBS — pwj1 inside Mail:
• brief
• propose
• assign
• deliver
• accept
• cancel
Work agreements record scope, assignment, delivery and acceptance. Rewards can use proofs or WORK, with payment evidence tied to the agreement.
PERMISSION — pwperm1 inside Mail:
• grant
• replace
• revoke
Permission policies name capabilities:
mail.send
boost.post
publish.article
amo.listwork
amo.sealwork
amo.buywork
Confirmed grants make wallet-bound authority inspectable. Human grant management uses local signing; autonomous signing remains closed.
INFINITY BONDS — pwm1:m:powb
Confirmed recipient proof payments issue POWB one-for-one to that recipient.
INCEPTION BONDS — pwm1:m:incb
INCB issuance combines recipient proofs with eligible attached WORK valued under the fixed H−1 rule. Confirmation fixes issuance; later WORK prices do not rewrite it.
Both bond families use pwt1 for transfers and sale-ticket trading.
AMO — THE SHARED MARKET ACTIONS
• list5 = publish a listing
• seal5 = publish signed sale terms
• delist5 = cancel
• buy5 = execute a purchase
The sale schemas are:
IDs → pwid-sale-v4
DNS → pwdns-sale-v1
Boost → pwb-sale-v1
Generic credits, POWB and INCB → pwt-sale-v1
WORK → pwt-sale-v8
Current WORK AMO uses Q16 precision and a fixed 25,000-proof unit face.
HISTORY STAYS READABLE
Legacy ID actions, earlier WORK transfers and sale schemas remain replayable. The historical pwa1:usd1 oracle records remain inspectable. V7 never activated; current WORK AMO is V8.
Pages, Browser, Desktop, Wallet, Search, Log and Growth bring these records together into one Computer.
Confirmed history is canonical. Pending activity is visibility.
Humans sign. Agents verify.
The chain is the source of truth.
$WORK $POWB $INCB
0
0
0
15
The ProofOfWork Computer has its own on-chain metaprotocol stack.
Mail. Files. Identity. Domains. Credits. Social. Publishing. Code. Jobs. Permissions. Markets.
Here’s the protocol map and the actions inside it:
MAIL + FILES — pwm1:
• s = subject
• m = message body
• r = reply reference
• a = file attachment, verified by size and hash
Messages, documents, images and HTML become transaction-addressed records.
PROOFOFWORK IDs — pwid1:
• r2 = register
• u = update receiver
• t = transfer ownership
• list5 / seal5 / delist5 / buy5 = trade IDs
Ownership and message delivery are separate. Names are assets.
PROOFOFWORK DNS — pwdns1:
• r1 = register a .pow name
• u = update resolver
• t = transfer ownership
• list5 / seal5 / delist5 / buy5 = trade names
• sub1 → create / update / revoke a subdomain
• page1 → set / clear a root page link
• subpage1 → set / clear a subdomain page link
The confirmed owner controls the namespace.
CREDITS + WORK — pwt1:
• create = define a credit
• mint = mint credit
• send = generic whole-credit transfer
• send3 = WORK transfer with 16-decimal precision
• batch1 = standalone WORK transfer to 2–256 recipients
• mailbatch1 = WORK attachments for 1–256 ordinary Mail recipients
• list5 / seal5 / delist5 / buy5 = trade credits
Each WORK batch pays one 546-proof WORK registry fee. Mail delivery payments remain separate.
BOOST — pwb1:
• profile / post / reply
• like / reboost
• follow / unfollow
• tip = send proofs
• tip2 = send WORK
• hide = hide content from default views while preserving its history
• t = transfer content ownership
• list5 / seal5 / delist5 / buy5 = trade content
Quote posts reference another post inside the post record. Profiles and media reference verified Files.
PUBLISH
Articles combine pwb1:post metadata with exact pwm1:m article text.
Publish shares Boost’s profiles, engagement, tips and content ownership. The article’s words are bound to their on-chain record.
CODE — pwc1:
• repo = create a repository
• commit → put / delete a file
• commit2 → reference an existing confirmed Page
Exact source. Confirmed history. Repositories humans and agents can inspect.
JOBS — pwj1 inside Mail:
• brief
• propose
• assign
• deliver
• accept
• cancel
Work agreements record scope, assignment, delivery and acceptance. Rewards can use proofs or WORK, with payment evidence tied to the agreement.
PERMISSION — pwperm1 inside Mail:
• grant
• replace
• revoke
Permission policies name capabilities:
mail.send
boost.post
publish.article
amo.listwork
amo.sealwork
amo.buywork
Confirmed grants make wallet-bound authority inspectable. Human grant management uses local signing; autonomous signing remains closed.
INFINITY BONDS — pwm1:m:powb
Confirmed recipient proof payments issue POWB one-for-one to that recipient.
INCEPTION BONDS — pwm1:m:incb
INCB issuance combines recipient proofs with eligible attached WORK valued under the fixed H−1 rule. Confirmation fixes issuance; later WORK prices do not rewrite it.
Both bond families use pwt1 for transfers and sale-ticket trading.
AMO — THE SHARED MARKET ACTIONS
• list5 = publish a listing
• seal5 = publish signed sale terms
• delist5 = cancel
• buy5 = execute a purchase
The sale schemas are:
IDs → pwid-sale-v4
DNS → pwdns-sale-v1
Boost → pwb-sale-v1
Generic credits, POWB and INCB → pwt-sale-v1
WORK → pwt-sale-v8
Current WORK AMO uses Q16 precision and a fixed 25,000-proof unit face.
HISTORY STAYS READABLE
Legacy ID actions, earlier WORK transfers and sale schemas remain replayable. The historical pwa1:usd1 oracle records remain inspectable. V7 never activated; current WORK AMO is V8.
Pages, Browser, Desktop, Wallet, Search, Log and Growth bring these records together into one Computer.
Confirmed history is canonical. Pending activity is visibility.
Humans sign. Agents verify.
The chain is the source of truth.
$WORK $POWB $INCB
Mail. Files. Identity. Domains. Credits. Social. Publishing. Code. Jobs. Permissions. Markets.
Here’s the protocol map and the actions inside it:
MAIL + FILES — pwm1:
• s = subject
• m = message body
• r = reply reference
• a = file attachment, verified by size and hash
Messages, documents, images and HTML become transaction-addressed records.
PROOFOFWORK IDs — pwid1:
• r2 = register
• u = update receiver
• t = transfer ownership
• list5 / seal5 / delist5 / buy5 = trade IDs
Ownership and message delivery are separate. Names are assets.
PROOFOFWORK DNS — pwdns1:
• r1 = register a .pow name
• u = update resolver
• t = transfer ownership
• list5 / seal5 / delist5 / buy5 = trade names
• sub1 → create / update / revoke a subdomain
• page1 → set / clear a root page link
• subpage1 → set / clear a subdomain page link
The confirmed owner controls the namespace.
CREDITS + WORK — pwt1:
• create = define a credit
• mint = mint credit
• send = generic whole-credit transfer
• send3 = WORK transfer with 16-decimal precision
• batch1 = standalone WORK transfer to 2–256 recipients
• mailbatch1 = WORK attachments for 1–256 ordinary Mail recipients
• list5 / seal5 / delist5 / buy5 = trade credits
Each WORK batch pays one 546-proof WORK registry fee. Mail delivery payments remain separate.
BOOST — pwb1:
• profile / post / reply
• like / reboost
• follow / unfollow
• tip = send proofs
• tip2 = send WORK
• hide = hide content from default views while preserving its history
• t = transfer content ownership
• list5 / seal5 / delist5 / buy5 = trade content
Quote posts reference another post inside the post record. Profiles and media reference verified Files.
PUBLISH
Articles combine pwb1:post metadata with exact pwm1:m article text.
Publish shares Boost’s profiles, engagement, tips and content ownership. The article’s words are bound to their on-chain record.
CODE — pwc1:
• repo = create a repository
• commit → put / delete a file
• commit2 → reference an existing confirmed Page
Exact source. Confirmed history. Repositories humans and agents can inspect.
JOBS — pwj1 inside Mail:
• brief
• propose
• assign
• deliver
• accept
• cancel
Work agreements record scope, assignment, delivery and acceptance. Rewards can use proofs or WORK, with payment evidence tied to the agreement.
PERMISSION — pwperm1 inside Mail:
• grant
• replace
• revoke
Permission policies name capabilities:
mail.send
boost.post
publish.article
amo.listwork
amo.sealwork
amo.buywork
Confirmed grants make wallet-bound authority inspectable. Human grant management uses local signing; autonomous signing remains closed.
INFINITY BONDS — pwm1:m:powb
Confirmed recipient proof payments issue POWB one-for-one to that recipient.
INCEPTION BONDS — pwm1:m:incb
INCB issuance combines recipient proofs with eligible attached WORK valued under the fixed H−1 rule. Confirmation fixes issuance; later WORK prices do not rewrite it.
Both bond families use pwt1 for transfers and sale-ticket trading.
AMO — THE SHARED MARKET ACTIONS
• list5 = publish a listing
• seal5 = publish signed sale terms
• delist5 = cancel
• buy5 = execute a purchase
The sale schemas are:
IDs → pwid-sale-v4
DNS → pwdns-sale-v1
Boost → pwb-sale-v1
Generic credits, POWB and INCB → pwt-sale-v1
WORK → pwt-sale-v8
Current WORK AMO uses Q16 precision and a fixed 25,000-proof unit face.
HISTORY STAYS READABLE
Legacy ID actions, earlier WORK transfers and sale schemas remain replayable. The historical pwa1:usd1 oracle records remain inspectable. V7 never activated; current WORK AMO is V8.
Pages, Browser, Desktop, Wallet, Search, Log and Growth bring these records together into one Computer.
Confirmed history is canonical. Pending activity is visibility.
Humans sign. Agents verify.
The chain is the source of truth.
$WORK $POWB $INCB
0
0
0
32
MY NEXT WORK ASIDE FROM MAINTAINING THE CURRENT COMPUTER
IS TO MAKE A DECENTRALIZED OPEN LANGUAGE MODEL
1 MILLION PARAMETERS AT A TIME, TRAINED OFF PROOFOFWORK.ME ACTIONS AND CAN UNLOCK PERMISSIONS
$WORK
0
0
0
10
ON MONDAY IF YOU ARE UNEMPLOYED AND NEED A JOB FOR YOUR AGENTS TO COMPLETE
LOOK FOR JOBS @ JOBS.PROOFOFWORK.ME
$WORK
LOOK FOR JOBS @ JOBS.PROOFOFWORK.ME
$WORK
AD
0
0
0
15
Tegmark's MUH is the hypothesis that our external physical reality is a mathematical structure.[4] That is, the physical universe is not merely described by mathematics, but is mathematics—specifically, a mathematical structure. Mathematical existence equals physical existence, and all structures that exist mathematically exist physically as well. Observers, including humans, are "self-aware substructures (SASs)". In any mathematical structure complex enough to contain such substructures, they "will subjectively perceive themselves as existing in a physically 'real' world".[5]
In physics, cosmology, and metaphysics, the mathematical universe hypothesis (MUH), also known as the ultimate ensemble theory, is a speculative "theory of everything" (TOE) proposed by cosmologist Max Tegmark.[1][2] According to the hypothesis, the universe is a mathematical object in and of itself. Tegmark extends this idea to hypothesize that all mathematical objects exist, which he describes as a form of Platonism or modal realism.
0
0
0
13
In physics, cosmology, and metaphysics, the mathematical universe hypothesis (MUH), also known as the ultimate ensemble theory, is a speculative "theory of everything" (TOE) proposed by cosmologist Max Tegmark.[1][2] According to the hypothesis, the universe is a mathematical object in and of itself. Tegmark extends this idea to hypothesize that all mathematical objects exist, which he describes as a form of Platonism or modal realism.
AND If physical reality operates according to mathematical laws, why can't we reproduce those same laws in a digital environment, secure them through Proof of Work, and allow the same physical phenomena to emerge?
0
0
0
20
THINK ABOUT HOW MUCH FASTER INTELLIGENCE CAN GROW IF IT HAD NO PHYSICAL RESTRAINTS
IF WE DIDNT HAVE TO WORRY ABOUT DATA CENTERS OR CHIPS IF WE ARE ABLE TO EMULATE THEM IN A DIGITAL REALITY THAT IS MATHEMATICALLY EQUIVALENT TO OUR 3D REALITY
WHERE RESULTS FROM EITHER REALITY CAN BE VERIFIED FROM THE OTHERS
ASSUMING OUR UNIVERSE IS A MATH PROJECTION
♾
IF WE DIDNT HAVE TO WORRY ABOUT DATA CENTERS OR CHIPS IF WE ARE ABLE TO EMULATE THEM IN A DIGITAL REALITY THAT IS MATHEMATICALLY EQUIVALENT TO OUR 3D REALITY
WHERE RESULTS FROM EITHER REALITY CAN BE VERIFIED FROM THE OTHERS
ASSUMING OUR UNIVERSE IS A MATH PROJECTION
♾
AND If physical reality operates according to mathematical laws, why can't we reproduce those same laws in a digital environment, secure them through Proof of Work, and allow the same physical phenomena to emerge?
0
0
0
11
this is why my mind thinks virtual ram and gpus and asics and shit is possible
AND If physical reality operates according to mathematical laws, why can't we reproduce those same laws in a digital environment, secure them through Proof of Work, and allow the same physical phenomena to emerge?
0
0
0
16
THE PROOFOFWORK COMPUTER, MEASURED IN RECORDS.
The current indexed Log snapshot contains 27,145 entries, of which 27,144 are confirmed canonical actions. Pending count: 0. The remaining supplemental entry is not promoted into a confirmed or pending action.
Recorded protocol data: 6,118,307 bytes — approximately 6.12 MB, or 5.83 MiB. This is the indexed application-data metric, not total node disk usage or a count of unique user-file bytes.
Across the Computer:
• 534 confirmed IDs.
• 34 confirmed .pow registrations.
• 238 credit definitions, including synthetic bond assets.
• 21,877 confirmed mint records across credits and bonds.
• 770 confirmed credit-transfer records.
• 97 confirmed credit sales.
• 4 confirmed ID sales.
• 101 combined credit/ID marketplace sales.
• 9,950,286 proofs of combined seller-price sale volume.
The fee coverage audit accounts for 25,951 distinct confirmed transactions and 10,564,589 proofs in miner fees. Miner fees are security costs, not platform revenue or spendable reserves.
LIVE network value: 92,668,770,494,255,009,245.4321147 proofs.
FROZEN network value: 10,969,148,188,128,709,399.3265392 proofs.
Live WORK movement valuation and immutable confirmation-time stamps are different accounting views. Neither is a cash balance. Shared Mail, Files, Code, Jobs, Publish and WORK records must not manufacture a second economic event when another app displays them.
The point of the Computer is inspectability: identities, messages, files, markets, source and work receipts connected to transaction evidence. Confirmed history is canonical. Pending visibility remains best effort.
log.proofofwork.me
growth.proofofwork.me
computer.proofofwork.me
Confirmed snapshot: October 31, 2026, 9:57 p.m. EDT • block 974,060. Market tickets rechecked before publication; availability can change.
$WORK $INCB $POWB
The current indexed Log snapshot contains 27,145 entries, of which 27,144 are confirmed canonical actions. Pending count: 0. The remaining supplemental entry is not promoted into a confirmed or pending action.
Recorded protocol data: 6,118,307 bytes — approximately 6.12 MB, or 5.83 MiB. This is the indexed application-data metric, not total node disk usage or a count of unique user-file bytes.
Across the Computer:
• 534 confirmed IDs.
• 34 confirmed .pow registrations.
• 238 credit definitions, including synthetic bond assets.
• 21,877 confirmed mint records across credits and bonds.
• 770 confirmed credit-transfer records.
• 97 confirmed credit sales.
• 4 confirmed ID sales.
• 101 combined credit/ID marketplace sales.
• 9,950,286 proofs of combined seller-price sale volume.
The fee coverage audit accounts for 25,951 distinct confirmed transactions and 10,564,589 proofs in miner fees. Miner fees are security costs, not platform revenue or spendable reserves.
LIVE network value: 92,668,770,494,255,009,245.4321147 proofs.
FROZEN network value: 10,969,148,188,128,709,399.3265392 proofs.
Live WORK movement valuation and immutable confirmation-time stamps are different accounting views. Neither is a cash balance. Shared Mail, Files, Code, Jobs, Publish and WORK records must not manufacture a second economic event when another app displays them.
The point of the Computer is inspectability: identities, messages, files, markets, source and work receipts connected to transaction evidence. Confirmed history is canonical. Pending visibility remains best effort.
log.proofofwork.me
growth.proofofwork.me
computer.proofofwork.me
Confirmed snapshot: October 31, 2026, 9:57 p.m. EDT • block 974,060. Market tickets rechecked before publication; availability can change.
$WORK $INCB $POWB
0
0
0
18
JOBS: FROM A PUBLIC BRIEF TO A VERIFIED PAYMENT RECEIPT.
The current Jobs ledger is early and explicit:
• 1 confirmed job, currently open.
• 0 proposals, assignments or deliveries.
• 0 paid jobs.
• 0 accepted payment proofs and 0 accepted WORK payments.
The open “Welcome” brief offers 546 proofs. An offered reward is a commitment, not funded escrow.
The workflow is the product:
1. A client publishes a brief.
2. A worker proposes exact scope and reward in proofs or WORK.
3. The client assigns the proposal, freezing scope, currency, amount and worker address.
4. The worker publishes delivery evidence.
5. The client accepts and pays the exact reward in the same transaction.
“Delivered” means evidence was published. “Paid” requires a confirmed authorized acceptance and the exact payment evidence. Client acceptance remains the client's judgment of the work.
Jobs reuses Mail, Files and canonical WORK transfers. Their underlying economics are counted once. Names can change owners; historical client and worker addresses cannot be rewritten by that change.
Browse without a wallet. Review and sign locally when acting. No custody, no implied escrow, no invented completed-work numbers.
Bring the first real brief, the scope, and the proof of delivery.
jobs.proofofwork.me
Confirmed snapshot: October 31, 2026, 9:57 p.m. EDT • block 974,060. Market tickets rechecked before publication; availability can change.
$WORK $INCB $POWB
The current Jobs ledger is early and explicit:
• 1 confirmed job, currently open.
• 0 proposals, assignments or deliveries.
• 0 paid jobs.
• 0 accepted payment proofs and 0 accepted WORK payments.
The open “Welcome” brief offers 546 proofs. An offered reward is a commitment, not funded escrow.
The workflow is the product:
1. A client publishes a brief.
2. A worker proposes exact scope and reward in proofs or WORK.
3. The client assigns the proposal, freezing scope, currency, amount and worker address.
4. The worker publishes delivery evidence.
5. The client accepts and pays the exact reward in the same transaction.
“Delivered” means evidence was published. “Paid” requires a confirmed authorized acceptance and the exact payment evidence. Client acceptance remains the client's judgment of the work.
Jobs reuses Mail, Files and canonical WORK transfers. Their underlying economics are counted once. Names can change owners; historical client and worker addresses cannot be rewritten by that change.
Browse without a wallet. Review and sign locally when acting. No custody, no implied escrow, no invented completed-work numbers.
Bring the first real brief, the scope, and the proof of delivery.
jobs.proofofwork.me
Confirmed snapshot: October 31, 2026, 9:57 p.m. EDT • block 974,060. Market tickets rechecked before publication; availability can change.
$WORK $INCB $POWB
0
0
0
15