Skip to content

fix: state how cursed dmt tokens are handled #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MJEND7 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: state how cursed dmt tokens are handled #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -570,7 +570,9 @@ The TAP Protocol indexer must properly index Bitmap as of the original specs, wi

TAP Protocol supports elements field 4 (block height), 10 (nonce) and 11 (bits) as of the DMT specs located at https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/digital-matter-theory

This includes the functions "dmt-deploy" and "dmt-mint" and work according to the DMT specs within the TAP Protocol.
This includes the functions "dmt-deploy" and "dmt-mint" and work according to the DMT specs within the TAP Protocol.

**Note:** No dmt token can be cursed **ever**, the prefix `-dmt` does not exist and was not valid before the [Jubilee](#the-jubilee) and is not valid now, being the case no cursed actions count should towards the indexer state.

From Bitcoin block 861,576 onwards, Blockdrops for DMT UNats and Bitmaps are supported.

Expand Down