DBCs design was based on nodes (called “elders” at that time) being the trusted mints. If we are talking about the Community Token (as opposed to Native Token), this is not possible, because Community Token design is totally in Autonomi’s application layer and does not involve modifying node software. DBCs are possible for Native Token, there is a StorPunk project, which aims for launching Native Token as close to DBCs as possible.
5 Likes
Do you happen to know where to look for the details of these designs?
1 Like
Not, because Public Key is an address of a future spend, and it’s one-time key, so if spend of first token is made, you cannot make another spend of second token from this key, because a transaction is already present at that key/address.
Now I’m a proud owner of the $FLATs, what a feeling!
Will a million be enough? Please, collect it at ae5ab47ba570c1db3c9f2c1c3872f100dc930ffd42bce845cb81f2b5dc4d950e85dfedcdfe534b08623bfe5e0dc2d010 
And a million for you, now there’s only 998 million left… : b4c2e0b3423833abdf34f7577ff4ffa9e943aa6a9b6937240ee25c49bdd12f8a0acbbb8d56dd44230f60c3d2ae2f2f6e.
2 Likes
Ouch, so that seems like a lost million… probably because when you requested it, you got a fork error so your request key was not saved into the wallet. Just try make another request for $TT2.
I always help anyone who wants to get rid of money. Here’s my request key: 99b1da63a4878f20630e80ecd6656664143ee5fbb8fdfe355e688f1c4cffc4200c7c67b1567bc21cd414c9d0b3d2e799
2 Likes
Crated spend: 8f29ff361c6e88f7faf956541843e88de7fba8f10179c4d4c3345800d4f5d7726c3b5948023cb9f982093d2d8e01feae
and my reqest for TT2
Public Key: 86d14531c1eb9c8ff618974392a2c337536526f1fcfbfe8856ee03426205f3bbd24066868c78cd062b72b1c2980cad26
2 Likes
My first hard-earned GRUMPs! Now that’s something, thanks
2 Likes
I accidentally clicked “Make payment” twice. I wonder if both of these spends will be receivable on your end:
9835ae0fca0cb208a6e92d983ead9d9a0d3f81df57387b34ab62146bc65d209265db12ca0dcd55846ca96de213eb95c4
849019f5b3b2fc48c7473e142d5d4e02246afd1557648efcb8a54f454ce438718959d26a7de69779747fab9d9b339687
Did you make a second request, or just copied the old key? When making request, a TT2: 0.0 should appear in your balances, which I don’t see on the screenshot. So if you’ve got through the “Request” screen, and haven’t got 0 balance, I think we spotted a bug
Let’s have some sleep, good idea.
2 Likes
I just cut n pasted from
Anyway night night
2 Likes
Really? I had understood that it was very temporary until they finish working on the token.
Without a native token, there cant be any privacy.
2 Likes
It had only been temporary temporarily 
1 Like
So are we at a point where some sort of fork would be required to respect the original promises? I must say that this is very disappointing. I have a lot of respect for the relentless work accomplished by the team, but if no native token is in the pipeline before the network is mainstreamed, we are talking about a major failure of the original plan. If true, the sugar coating of selling it as “temporary” would really add insult to injury.
3 Likes
Well, first of all, it would be nice if the team/Mr. David came out and spoke on the issue in a clear, coherent fashion. No hints, no innuendos.
It went from
definitely, because anonymity and freeeeedoom!!!→not yet→not soon→maybe not ever→never said never→we would get imprisoned, do you want us to get imprisoned?!
There are signs of people realizing forks will be inevitable, but the project rarely leaks anything that makes things clear.
1 Like
Yes really, David stated this a few weeks ago.
It is I assume why they dropped DBCs and spent months working on a DHT based native token before giving up and switching to a Blockchain solution.
Though I don’t recall them explaining why they dropped DBCs at the time, David also said that it had been made clear at some point.
So those wanting to stick to the fundamentals have the following problems:
- needing someone willing to take on the personal risk of implementing a privacy token
- any technical difficulties with the current network (the design of which has changed as pointed out by @loziniak)
- getting a rival network off the ground in the face of legal risks and against the Autonomi network, it’s marketing budget, established reputation, momentum etc
The fundamentals are no longer a realistic proposition IMO, so I continue to try to get as close to them as possible, focusing mostly on web and app features, and access for everyone.
I’ve asked Autonomi to explain the privacy claims for uploaders, downloaders and noderunners on two or three occasions recently but not seen any response. So I don’t know how close we can get.
But if the token is not private the claims seen tenuous or false for anyone transacting the token, so uploaders and noderunners.
Perhaps others will have more luck, by asking how private when such statements are made. I’d certainly welcome this being clarified because I don’t feel good claiming something I don’t understand and have doubts about. So I no longer claim privacy as a feature. Still lots to like, or I wouldn’t be here.
4 Likes
Thanks, @happybeing . This is very disappointing. Is there any reference to clarify that they actually dropped the plan to build a native token?
If so, I can’t avoid feeling betrayed. I supported them from the beginning, including trough Bnktothefuture and they now unilaterally break one of the fundamental promises. I dont wish anyone bad and apprciate the work accomplished, but it is still a major betrayal of the backers.
2 Likes
I didn’t say they’ve dropped native token, just DBCs or any privacy token.
I didn’t keep a link to David’s statement. I think it was on Discord and mentioned “prison” so someone you might be able to find it.
1 Like
This should be the one: https://discord.com/channels/1209059621319221268/1209059622586163272/1399865655313830079”
2 Likes