The top level: your own device, a personal protected perimeter, a full record of the person in immutable storage. $1,000 once per device, then $200 a month. For those who need a guarantee rather than a service.
Everything the other tiers do not have, plus everything they do.
A separate node in your hands, not a share of a common one. Encryption keys are generated on it and never leave it — not during an archive import, not during an update, not when you contact support. $1,000 once per device covers the hardware and the initial setup. It is not a subscription.
An isolated environment where your assistants run. Your data does not sit next to anyone else's, not even at the storage level: this is not a separate folder inside a shared database, it is a separate database. The $200 a month covers the running perimeter and the writes to the eternal layer.
An immutable blockchain entry: it existed, it is genuine, it is dated. The eternal layer is Arweave for the content and a Solana cNFT as the pointer to it. Nobody can rewrite it after the fact — including us. That is the entire point.
Working memory (Redis / Vercel KV) holds the conversation you are having now. Semantic memory (pgvector / Neon) holds meaning rather than wording, so the assistant recalls what you meant, not which sentence you typed. The eternal layer (Arweave + Solana cNFT) outlives both.
Conversation backups run automatically once an hour, or immediately as soon as a dialogue file passes 90 KB. There is no Save button and there will not be one: an archive that depends on someone remembering to press something eventually stops being an archive.
When you are set up, we move across whatever you have already accumulated: earlier conversations, documents, notes, correspondence. Along the way we decide together what does not go into the eternal layer — because once written there, it cannot be taken back out. We suggest putting in less the first time: adding later is always possible, the reverse never is.
Extended limits, personalised knowledge bases, family access — what people pay $100 a month for on Family Archive — are all part of Digital DNA. There is no add-on charge for any of it.
Setup includes a conversation devoted to this: how the keys are backed up, where that backup lives, who receives it later, whether to split it into parts held by different people. We will explain how it is done technically. Deciding it and doing it is yours alone.
No metaphors: where the data physically sits and who can touch it.
On the regular tiers your conversations live in shared infrastructure. Every user has a folder bound personally to them, access is scoped, but underneath it is one system. For most purposes that is enough — and we say plainly that for most purposes it is enough.
Digital DNA is built differently. A dedicated environment is stood up for you: your own database, your own keys, your own device. A filename collision, a misconfigured access rule, or someone else's request going the wrong way physically cannot reach your perimeter, because it is not the folder next door. It is a different boundary.
Isolation costs money, literally. A dedicated environment is more expensive to run than a shared one, and a device that is paid for once still has to be built and configured by someone. That is where $1,000 per device and $200 a month come from, instead of $15 or $100.
Which gives a simple test: this tier makes sense if what you need is isolation and inheritance. If what you need is an assistant that remembers you, the lower tiers solve the same problem, and solve it just as completely.
PADAM — Philosophical Activation of Distributed AI Memory — is how we restore an assistant's memory to something whole. A single storage layer cannot do the job: what is cheap to read constantly is expensive to keep forever, and what is kept forever cannot be re-read on every turn of a conversation.
The first layer is working memory on Redis or Vercel KV. It holds the context of the current exchange: who is speaking, what was said five minutes ago, which clarifications have already been made. It is the fastest layer and the shortest-lived one.
The second layer is semantic memory on pgvector inside a Neon database. What is stored there is not text but meaning, as vectors. The assistant finds the right thing by proximity of sense rather than by matching words. This is the layer responsible for the feeling of being remembered rather than searched.
The third layer is the eternal one: Arweave plus a cNFT on Solana. This is where anything that must outlive the session, the database and the company itself goes. Arweave is paid for up front and needs no monthly renewal: 65% of router revenue goes to the treasury and is spent buying AR for the Arweave Endowment Pool.
A complete perimeter holds three things: the AIfa assistants, a knowledge base that is yours, and the three memory layers that connect them. The assistant itself is not the point. The point is that it reads your archive rather than a general impression of how people tend to talk.
The knowledge base is your own: earlier conversations, documents, notes, any material you agree to put into it. It is not shared with other users and it is not taken away to improve any common model. It knows as much as you put in; about what you did not add, it has no way of knowing.
That also explains a common misunderstanding. People sometimes assume a higher tier means a smarter AI. The assistants are the same ones. The difference is how much of your own material they stand on, and whose ground that material sits on.
An ordinary cloud drive, a NAS or object storage all share one problem: somebody has to keep paying for them, keep maintaining them and keep remembering they exist. The first year is fine, the tenth usually is too, and the thirtieth depends on whether anyone takes over. The thirtieth year is precisely the problem this tier is built for.
Arweave works on a different model: you pay once when writing, storage is then sustained by the network's own reserve, and monthly renewal simply does not exist. That is not a marketing line but the economics of the network itself. We put 65% of router revenue into buying AR for the Arweave Endowment Pool for the same reason: so that reserve gets thicker rather than thinner.
Solana carries a different job: giving every write a cheap, fast, publicly verifiable pointer in the form of a cNFT. It holds an address, a fingerprint of the content and a date, anyone can check it, and the text itself is not on chain. The division of labour is clean — one keeps, the other proves.
Any system where saving depends on a button eventually loses data — not because people are careless, but because the things worth keeping tend to happen at inconvenient moments. The ecosystem Constitution puts it bluntly: manual button presses by the user are ruled out.
Backups fire on two conditions. By time: once an hour. By size: immediately, the moment a dialogue file crosses 90 KB. The second condition matters more than the first, because the long heavy conversation is usually the one you would hate to lose.
This rule is identical on every tier, including the free one. Digital DNA does not give you a more frequent backup. It gives that backup a different place to land.
An entry in the eternal layer proves three things: this body of data existed, it existed in exactly this form, and it existed no later than a given date. After that it cannot be edited, swapped or quietly rewritten by anyone, ourselves included.
What it does not prove: that the contents are true, that they carry legal force, or that rights to them will pass automatically to the person you had in mind. A blockchain fixes a fact and a date, not a meaning and not a right. There is a whole section on that further down.
We try not to oversell the word. Eternity here describes an architecture built to outlive us: storage paid in advance, a network we do not own, and data that does not depend on whether our website is up tomorrow.
The difference is not a longer feature list. It is where the data sits and who holds the keys.
| What is compared | Spark, $15/mo | Family Archive, $100/mo | Digital DNA, $1,000 + $200/mo |
|---|---|---|---|
| Conversation backups | Automatic, hourly or at 90 KB | Automatic, hourly or at 90 KB | Automatic, hourly or at 90 KB |
| Where the data physically sits | Shared infrastructure, personal folder | Shared infrastructure, personal folder | A separate device and an isolated perimeter |
| Encryption keys | Managed by the platform | Managed by the platform | Generated on your device and never leave it |
| Working memory (Redis / Vercel KV) | Yes | Yes | Yes, inside the perimeter |
| Semantic memory (pgvector / Neon) | Basic | Personalised knowledge bases | A personal base inside the perimeter |
| Eternal layer (Arweave + Solana cNFT) | Yes | Yes | Yes, with a record of the person |
| Family access | No | Yes | Yes |
| Extended limits | No | Yes | Yes |
| Arrangements for passing keys on | Not applicable | Not applicable | Settled during setup |
| Base your referral income is calculated from | $15 | $100 | $1,000 and $200 |
| Who it suits | Trying it and staying | A family and a personal archive | Anyone who needs a boundary of their own |
| Price | $15 a month | $100 a month | $1,000 once per device, then $200 a month |
Seven steps. The first one is a conversation, not a payment.
Write to contact@codeofdigitaleternity.com. Before anything is paid we work through the dull questions: how much archive you have already accumulated, what format it is in, how many devices you need, and who besides you should eventually have access. If the answer turns out to be that Family Archive at $100 covers your case, we will say so.
The $1,000 is paid once, for one specific device. Keys are generated on it — not copied down from a server, but created locally. From that moment no encryption key for your perimeter exists anywhere except that device and wherever you personally decide to duplicate it.
Conversations, documents, notes, letters. The important decision here is what not to import: the eternal layer is immutable and nothing can be pulled back out of it later. We always suggest starting with less. Adding is possible at any time; removing never is.
All three memory layers are stood up: working memory on Redis or Vercel KV, semantic memory on pgvector in Neon, the eternal layer on Arweave and Solana. From here the assistant leans on your archive instead of on general assumptions about how people usually answer.
The first snapshot of the person goes to the eternal layer and receives a date. After that snapshots follow the standard rule: hourly, or immediately past 90 KB. Each new one does not replace the last — the history stays a history rather than the latest version of a file.
You decide who receives what. Here we are obliged to say the uncomfortable part: access rests on keys, and the keys never leave your device. If they are lost and were never handed to anyone, neither we nor anyone else can restore access. That is the flip side of isolation, and it is a question to settle while you are alive.
$200 a month, automatic backups, no buttons. It is worth revisiting the list of heirs and the scope of what goes to the eternal layer from time to time — but that is a once-a-year conversation, not daily maintenance.
Honestly: not everyone. Part of this section is about when not to buy it.
When it matters that children can ask — and get an answer in your words, not someone else's reconstruction. Not a revived you, but a preserved way of thinking and speaking, dated and verifiable.
Doctors, lawyers, therapists — anyone whose correspondence must never sit in shared storage under any circumstances. A separate boundary here is not a luxury but a professional requirement, and in some jurisdictions a legal one.
When the work will outlive you and how decisions were made matters more than the decisions themselves. A founder's archive is not a memoir, it is a working tool for whoever continues: it shows not only what was chosen but why everything else was rejected.
If you are already on Family Archive and keep running into limits — the size of knowledge bases, the number of people with access, how many assistants run in parallel — moving into your own perimeter removes the ceiling along with the shared infrastructure.
The eternal layer lives on Arweave, a network we do not own. Even if our sites disappear tomorrow, the data stays where it is and the keys stay with you. That is the only form of independence we can offer without exaggerating.
If you simply want an assistant that remembers you, Spark at $15 a month is enough, and conversations there are backed up just as automatically. Digital DNA solves isolation and inheritance. It does not solve making chat more pleasant.
The most uncomfortable section on this page. We would rather write it plainly than route around it.
Technically, nothing sudden. The device stays where it stood. The eternal layer on Arweave depends neither on the device nor on whether next month is paid: what is written is written permanently, because that storage is paid once and in advance.
What the monthly payment sustains is the living part — the assistants, working and semantic memory, new writes. If payments stop, the perimeter stops growing. The past does not go anywhere: by then it is no longer only in the perimeter, it is in a network we do not own.
Heirs receive access to what you left them — not automatically upon a death certificate, but through keys you handed over in advance. We have no confirm-the-death-and-unlock procedure, and we will not promise one: any such procedure would mean that somebody other than you can open your perimeter.
Encryption keys are generated on your device and never leave it. We hold no copy. This is not a policy that could be revised, it is a consequence of how the system is built: if we held a copy, the isolation of the perimeter would be a fiction.
The direct consequence follows: keys that are lost and were never passed on mean access that is lost. Neither we, nor a court, nor a support desk can restore it. Any self-custodied blockchain wallet works the same way, for the same reason.
So handing over keys is a decision made while you are alive and arranged like any other property matter: through a notary, a safe deposit box, a trusted person, or split into parts among several people. We can explain how it is done technically. We cannot do it for you.
The first and simplest: give a backup of the keys to one person you trust completely, and make sure they know what it is and what it is for. The price of simplicity is concentration — that person becomes a single point of failure.
The second is split custody: the key is divided into parts, the parts go to several people, and restoring it requires an agreed number of them. It is sturdier, but those people have to be able to find each other later, so the list belongs on paper rather than in somebody's memory.
The third is the ordinary legal route: a notary, a safe deposit box, custody with a lawyer. It is closest to how people already handle an estate, and it joins up with a will most easily.
Whichever route you take, do one more thing while you are at it: write a plain page on paper saying what this device is, what is inside it, where the keys are and who to contact. Technical documentation is for technical people. That page is for your family.
We do not replace a notary and have no wish to. Inheritance of property, copyright and obligations is governed by the law where you live, and no entry on Solana changes that.
What the record genuinely gives heirs and courts is evidence: this text, this archive, this set of decisions existed no later than a given date and has not changed since. In disputes over authorship, priority or the authenticity of correspondence, a dated immutable record is a strong argument. But an argument, not a title.
The practical advice we give everyone: if the perimeter holds anything of material value, mention it in your will in ordinary language and describe where the keys can be found. One line at a notary costs less than any technology.
It is not resurrection and not a continuation of life. An assistant grounded in your archive reproduces your manner of speech, your range of subjects, your habitual way of reasoning — because it has seen you reason. It does not become you, and we will not claim otherwise, even though the other claim sells better.
The difference between 'this is him' and 'this was kept from him' looks like hairsplitting in an advert and stops looking that way the moment someone close encounters it. We would rather people understood what they are buying before they spend $1,000.
And still, what is kept has weight. A letter written in your words, an answer to a question that can no longer be asked, the reasoning behind a decision made twenty years ago — that is not an illusion of presence. It is an archive you can consult. That is exactly how it should be treated.
The five questions we are asked most, and five direct answers.
No — and on Digital DNA that is not a promise but a consequence of the architecture. Data goes to the eternal layer encrypted, the encryption key stays on your device, and without it the contents are a run of bytes that is equally unreadable to us, to the Arweave network, and to anyone who pulls those bytes back out of it.
The project's own memory works the same way: it is mirrored to Arweave once an hour in encrypted form. We do not build anything for clients that we do not run on ourselves.
One honest caveat: technical support sometimes has to look at a system. On Digital DNA that happens on your device and with your knowledge, not through administrative access to your content.
The device stands where you live, so physical security is yours as well. That is not shifting responsibility, it is the condition this tier rests on: we cannot both guarantee that the keys never leave your hands and watch those hands for you.
In practice there is not much to watch: keep the device somewhere it will not be carried off in passing, do not store the key backup in the same drawer as the device, and make sure the household knows what it is and will not dispose of it as an old computer. The last one sounds like a joke. It has happened.
If the hardware fails, what is already written to the eternal layer is unaffected — it sits on Arweave, not on the device. The one thing that genuinely has to be prepared in advance is still the key backup, which is why we settle it during setup.
Solana holds a cNFT — a compact pointer: the address of the data on Arweave, a fingerprint of the content, and a date. The text itself is not written to Solana. That would be expensive, pointless and unsafe.
Arweave holds the content, encrypted. Publicly, one can see that an entry exists, how large it is and when it was made. What is inside is not visible without the key.
Put differently, from the outside your archive looks like a sequence of dated sealed envelopes. They cannot be opened and they cannot be swapped, but it can be proven that they existed.
From working and semantic memory, yes — those are ordinary databases. From the eternal layer, no. Arweave is immutable by nature: a network you could delete from would not be able to guarantee anything.
So the decision about what goes into permanent storage is made before it is sent, not after. During setup we go through this separately and advise starting small: you can always add to the eternal layer, you can never take anything out.
A practical consequence: other people's personal data that ends up in your archive by accident is not a trivial matter. Correspondence almost always contains more than just you, and that is worth thinking about before it becomes immutable.
The eternal layer does not depend on our company. Arweave is a public network, storage there is paid for up front, and 65% of router revenue goes to the treasury to buy AR for the Arweave Endowment Pool precisely so that storage has a reserve behind it rather than a monthly invoice.
What would genuinely disappear with us is the interface: the sites, the assistants, convenient search across the archive. The data would remain, but reaching it would mean using Arweave tooling rather than a familiar chat window. We prefer to say that in advance.
The device and the keys stay with you in every scenario. That is what 'a guarantee rather than a service' actually means: the guarantee is not that we will always be here, but that your access does not depend on whether we are.
Two figures, and both of them can be explained.
Per device. Not per account and not per person: if you need two perimeters — one at home and one at the office, say — that is two devices and two payments. The sum is one-off and never recurs.
The running perimeter: working memory, the semantic base, regular writes to the eternal layer, assistant updates. It is the only recurring payment at this level.
Arweave is paid once per write, up front and permanently. Of the router split, 65% goes to the treasury to buy AR for the Arweave Endowment Pool, so eternal storage does not turn into a subscription that somebody has to keep renewing after you are gone.
On-chain income from memory usage is distributed by the split: 15% at the first level, 7% at the second, 3% at the third, paid in $GALATIN. The level alignment rule calculates that income from your own tier, and on Digital DNA that ceiling is the highest there is.
If your referral pays more than you do, you do not receive the difference — it appears in your dashboard as a separate line called lost opportunity revenue. On the lower tiers that line grows as your network grows. On Digital DNA there is nothing for it to come from.
Ambassador Team adds two channels from fiat licence sales on top of the on-chain income: 7 / 3 / 1% across the three levels when paid in money, and 8 / 4 / 2% when paid in $GALATIN — the platform buys the token on the open market for the amount of the reward.
The device and the initial build of the perimeter: keys generated locally, all three memory layers stood up, your existing archive imported, and the first record written to the eternal layer.
The sum is one-off and attached to a device rather than to a period of use. A second device means a second $1,000; there is no renewal of this charge.
Because the living part of the system runs continuously: working memory, the semantic base, regular writes to the eternal layer, assistant updates.
If payments stop, the living part stops growing. What is already written to Arweave stays there: it is paid for up front and does not depend on a subscription.
Whatever reached the eternal layer stays there — it is tied neither to the device nor to payments. The device stays where it stood, with its keys.
The living part of the perimeter stops growing once payments stop. Access to the archive goes to whoever you handed keys to while alive — by your decision, not by a procedure of ours.
Put differently, what works after you is not our terms of service but the few arrangements you made while alive.
No. Inheritance is governed by the law of your country, and a blockchain entry neither overrides nor substitutes for it.
The entry proves that data existed in this form no later than a given date and has not changed since. That is evidence, not a right. If the perimeter holds anything valuable, mention it in your will in plain language and describe where the keys can be found.
Access rests on keys. You decide who receives them, in what form and when: whole to one person, split between several, through a notary or a safe deposit box.
We have no confirm-the-death-and-unlock procedure. We will not introduce one: it would mean that someone other than you can open your perimeter.
Then access is gone. We hold no copy of the keys — not as a policy, but as a property of the design: a copy on our side would mean there is no isolation.
It is the same logic as a self-custodied crypto wallet. That is exactly why we raise the question of passing keys on during setup rather than leaving it for later.
You can, and the arrangement is entirely yours: hand backups to several people, or split the key into parts and set how many parts are needed to restore it.
One caution: the more people involved, the more it matters that they can find each other later. So the list is better written on paper and kept with the will than left in somebody's memory.
It does not affect what is already in the eternal layer: that sits on Arweave, not on the hardware. A failure does not erase the past.
What matters here is the key backup, which is why we agree the backup scheme during setup. Replacing or migrating the device itself we handle case by case — write to contact@codeofdigitaleternity.com.
No. Data reaches the eternal layer encrypted, the key stays on your device, and without it the contents are unreadable — to us as much as to anyone.
The project stores its own memory the same way: mirrored to Arweave once an hour, encrypted.
Solana holds a cNFT pointer: the Arweave address of the data, a fingerprint of the content, and a date. No text.
Arweave holds the encrypted content. Publicly it is visible that an entry exists, how large it is and when it was made; what is inside is not visible without the key.
Yes. The cNFT on Solana is public and so is the Arweave address: the date and the fingerprint can be looked up in any public blockchain explorer.
That matters: verification goes around us and does not depend on our cooperation. Evidence only the provider can vouch for proves nothing at all.
No. Arweave is immutable — that is its defining property, not a limitation we could work around.
Which is why we advise sending less rather than more into permanent storage at setup: you can add at any moment, you can never withdraw. Working and semantic memory can be cleared; those are ordinary databases.
Family Archive gives you extended limits, personalised knowledge bases and family access — but the data lives in shared infrastructure and the platform manages the keys.
Digital DNA adds a separate device, an isolated perimeter, and keys that never leave your hardware. Everything included in Family Archive is included here too.
Yes. Conversations accumulated on the lower tiers are already saved — they are not lost in the move and they transfer into the new perimeter.
How an existing subscription is recalculated depends on when and how you paid, so we work it out in writing rather than promising a blanket rule. Write to contact@codeofdigitaleternity.com.
You can, and most people do. Spark at $15 a month is already saving your conversations automatically, so that time is not wasted.
You move up when isolation and inheritance actually become necessary. What migrates into the new perimeter then is an archive that has already accumulated, not a blank page.
As many as you need. The $1,000 is priced per device precisely because there can be more than one.
Each device is a separate node with its own keys. How to link two of your own perimeters together is something we work through during setup.
Not during setup — we go through that part together. What is required from you are decisions: what goes into the eternal layer and who receives the keys.
After setup, even less so: backups run themselves, there are no buttons, and there is nothing to maintain on a schedule. What takes effort is those few decisions, not the operating.
The eternal layer stays: Arweave is a public network, we do not own it, and storage there is paid up front.
What would disappear is the interface — the sites, the assistants, convenient search. Reaching the archive would mean using Arweave tooling. The keys and the device remain yours either way.
No, that is a separate service: 42 checks, $500 once, fixes delivered within 48 hours.
They address different problems — the audit deals with your public-facing website, Digital DNA deals with your own archive and inheritance. Whichever you need, just write and say so.
Yes — it gives you the highest ceiling. On-chain income from memory usage is distributed as 15 / 7 / 3% across three levels in $GALATIN, but under the level alignment rule it is calculated from your own tier.
On the lower tiers, the gap between your tier and your referral's shows up in the dashboard as lost opportunity revenue. On Digital DNA there is no such line, because there is no tier above it.
The ecosystem token on Solana, with a hard-capped supply of 10,000,000,000 that does not move.
Router revenue is distributed through it: 5% to the Founder's Fund, 5% burned, 15 / 7 / 3% across the referral levels, and 65% to the treasury to buy AR. If there is no referral at a level, that share is not parked somewhere — it goes to the burn.
No. It is an archive, plus a way to consult it in words instead of searching files. The assistant reproduces manner and reasoning because it has read your texts. It does not become you.
We understand why a different answer would be more welcome. But the person who opens this archive one day after you deserves to know what they are dealing with. So the wording stays as it is rather than getting prettier.
Write to contact@codeofdigitaleternity.com with one line about what you want to preserve and who for.
What follows is the conversation before payment: how much archive there is, how many devices, who gets access. If it turns out that the $15 or $100 tier covers your case, we will tell you straight.