defensive publication
Published, timestamped, open
This registry is a public, timestamped disclosure. Each sequence is published in full, with the date it was proposed and a hash anyone can recompute — the standard shape of a defensive publication, which is how disclosed material enters the public record and becomes citable prior art.
No patent has been filed on any sequence here, and none will be. What this registry does is publish and timestamp. What any particular disclosure would do to a specific later patent application is a question for a patent attorney and a patent office, and this page does not answer it.
The ledger
| id | sequence | class | proposed | sha-256 | on-chain anchor |
|---|---|---|---|---|---|
| BLLM-C001 | LKKTETIEQEKQAGLVQPGKPDMAEIEKQAGEPPG | healing | 2026-09-01 | 9839d67d39e13c20800667e53518ac5974449bdaf369442971e0b23d37d6faae | anchoring begins at launch |
| BLLM-C002 | LKKTETIEQEKQAGLVQPGKPD | healing | 2026-09-01 | bc96f27e9699f6b17326a73bb23cfd66f472291afac4a02bd14bf9929eccb7e2 | anchoring begins at launch |
| BLLM-C003 | LKKTETIEKQAGESQGTFTQE | healing | 2026-09-01 | e302b1994143dfe5d136b71eb70a2cbba081283d64b3ad4bca7e21e2a82b256f | anchoring begins at launch |
| BLLM-C004 | LLGDFFRKRIKDFFRKRQQELDKWASLIHSLWNWFTSSEI | immune | 2026-09-01 | 35ca9a3c18716617dcb6c446f2dc6ed84959ecdad4048f685ac0973daf76805b | anchoring begins at launch |
| BLLM-C005 | YTSSEITTKDFFRKSGAVDTSLIHSLWNWFAYRKSQNQQE | immune | 2026-09-01 | b5ef9c9f2e510b69cef7aa61b2f695005b0753fce65a9a42a2c7e30ad77369f4 | anchoring begins at launch |
| BLLM-C006 | SDAAVDTSSEITTGLPGTCGLPGTCLKSGAICHPV | immune | 2026-09-01 | f00089fcf9f84a035b167df750c63b3b280077bcb4f3cb534173c5ea62f29489 | anchoring begins at launch |
| BLLM-C007 | EDGSFR | longevity | 2026-09-01 | 1fee88d0b9ced962d2389e59a4e99736ca21bf43f01b2475b2e14f9393c6f383 | anchoring begins at launch |
| BLLM-C008 | EDGSFR | longevity | 2026-09-01 | 1fee88d0b9ced962d2389e59a4e99736ca21bf43f01b2475b2e14f9393c6f383 | anchoring begins at launch |
| BLLM-C009 | MAPRKLRIVQQEMGYIFYP | mitochondrial | 2026-09-01 | db6ad6c1ec7aa1705577330a114a7591d2842d27c04f7ca8a7c9e364cfac781c | anchoring begins at launch |
| BLLM-C010 | MAPRKLRISWIKDFIEWLKNGG | mitochondrial | 2026-09-01 | 6c1a20d3c5e95e597ebcc8731a4df966a3f642615da88649a69031e0150b4c5a | anchoring begins at launch |
| BLLM-C011 | MAPRKLRNLISDAIFYPR | mitochondrial | 2026-09-01 | e854517a9a39b4f583e32668a9110f04adae8e7287a955ac0504d94084e5877a | anchoring begins at launch |
Verify it yourself
Take any sequence from the table and hash it. You should get the value in the ledger:
printf '%s' 'LKKTETIEQEKQAGLVQPGKPD' | shasum -a 256
No trust required — that is the point of publishing a hash rather than asserting one.
How anchoring will work
At launch, each hash is written into the calldata of a transaction on Robinhood Chain from the project address, and the resulting transaction hash is recorded in the anchor column above. That gives every sequence a timestamp anyone can check against the chain, independent of this website continuing to exist.
Until a transaction actually exists, the anchor column says so. There are no placeholder transaction hashes on this page, because a fake anchor would defeat the entire mechanic.