788 posts

[email protected]

@proofofworkme

Building the Bitcoin Computer @ https://t.co/IOZmqyW3sa Register Your PoWID @ https://t.co/tRK4wmRlME Open Agent Development Standard (OADS)

Singularity Присоединился Mayıs 2026

70 Подписки67 Подписчики

Закреплённый твит

[email protected]@proofofworkme·2d

NPM INSTALL NPM RUN DEV THE BITCOIN COMPUTER IS ALIVE $BTC github.com/proofofworkme/…

English

2.4K

[email protected]@proofofworkme·3h

1/ ProofOfWork ID transfers are now live. A ProofOfWork ID is not just a username. It is a Bitcoin-native asset registered through OP_RETURN and resolved by the ProofOfWork registry. That means IDs can move from one owner to another on-chain. 2/ Every ID has two important fields: Owner: the address that controls the ID asset. Receiver: the address where messages sent to the ID are delivered. This lets someone own an ID while routing mail somewhere else. 3/ A transfer changes ownership. Example: bitcoin@proofofwork.me Current owner signs a transfer to a new owner address or another confirmed ProofOfWork ID. The app resolves the target, builds the registry transaction, and writes the transfer event on-chain. 4/ The transfer uses the same canonical registry address as registrations. Registrations cost 1,000 sats. Transfers and other ID mutations cost 546 sats. That keeps the registry simple: one address, one event stream, one canonical history. 5/ The transfer event is written as a ProofOfWork ID protocol OP_RETURN: pwid1:t::: If no new receiver is provided, the new owner also becomes the receiver. Clean, small, and permanent. 6/ The current owner must fund/sign the transfer. The resolver checks that the transaction was spent from the current owner address. That prevents random people from transferring IDs they do not control. Bitcoin itself becomes the authority layer. 7/ After broadcast, both sides now see the pending state. The sender sees an outgoing pending ID transfer. The receiver sees an incoming pending ID transfer. But it is not final until confirmed in a block. 8/ Once confirmed, the registry updates canonical ownership. The old owner no longer controls the ID. The new owner does. Future messages to that ID route to the confirmed receive address. Pending state is visibility. Confirmed state is truth. 9/ This is what makes ProofOfWork IDs different. They are not database usernames. They are transferable Bitcoin-native identity assets with public history, local wallet signing, and no account server controlling ownership. The final network. computer.proofofwork.me id.proofofwork.me

English

[email protected]@proofofworkme·3h

ProofOfWork ID transfers are live. You can now transfer an ID on-chain, and both sides see the in-flight state before confirmation: outgoing for the current owner incoming for the new owner / receiver confirmed ownership after block confirmation IDs are starting to behave like real Bitcoin-native assets. computer.proofofwork.me id.proofofwork.me The final network.

[email protected]

Открыть