Update 16 September, 2021

[Josh]

@maidsafe

DBC Mints

Who’s writing these DBC explainers, I am guessing @danda? Thank you.

I hope this series will not get lost in old updates and will be published on the website or elsewhere for easy access!

[dirvine]

@Josh

I am guessing @danda?

Yes, a skill for sure. I like the accuracy and exact nature of these, David Rusu helps too with the digrams and more. They are the DBC squad right now

[Southside]

@Josh

I hope this series will not get lost in old updates and will be published on the website or elsewhere for easy access!

Possibly a job here for the community, collating the best bits …

[happybeing]

An opportunity for anyone who thinks they don’t have technical or other skills needed to contribute.

The reality is there’s always a way for anyone to contribute.

[danda]

that would be great. We have also had the thought that as we get a bit further along with fleshing out the entire DBC system, it would be good to write a whitepaper detailing how it works, and this dev update series could serve as a starting point for that.

[mav]

@Lisa_Brown

I just want to know, @maidsafe , what are your gut feelings? Is this going to work? Can somebody throw us a bone?

I can’t speak for maidsafe but here’s my personal view on it.

It will probably work.

At the core it’s ‘just a chat system for machines’. They tell each other what to do and if they don’t do it they tell each other about that. Sometimes people chat too (uploads / downloads) but right at the root of it is machines saying ‘do we agree about stuff’.

If someone starts talking trash, the machines can cope.

If lots of trash comes all of a sudden the machines can probably still cope.

If almost everything is trash, the system is kinda pointless isn’t it. Do we say it failed? Probably. But not because machines couldn’t chat, it was because people only wanted to talk a lot of trash. Maybe this is shifting goalposts. It becomes kinda fuzzy.

The actual mechanisms for ‘coping’ have some pretty complicated ways of playing out. The mechanisms themselves are simple, but the behaviors they lead to are not.

@MrKeepingItSafe

are the team any bit close to a working test net?

Closer for sure. But when do we get to a testnet that’s useful? I dunno. Gut says maybe a month? Really don’t know though. I haven’t run a local testnet for several months now so am not well positioned to judge how stability is changing.

@Silent_Follower

As far I understand, the priority for the next testnet is stability. What is missing? Are there persisting some bugs?

Yep, bugs. That’s the main thing missing for a stable testnet, squashing as many bugs as necessary for stability. The underlying ideas are there, but bugs are making things fall over.

[Southside]

@mav

At the core it’s ‘just a chat system for machines’. They tell each other what to do and if they don’t do it they tell each other about that. Sometimes people chat too (uploads / downloads) but right at the root of it is machines saying ‘do we agree about stuff’.

If someone starts talking trash, the machines can cope.

If lots of trash comes all of a sudden the machines can probably still cope.

I like it - cut n pasted for now

[anon23746431]

@maidsafe

Distributed Spentbook written by Client

This is a feature in development. The basic idea is that the Client commits to a given ReissueTransaction and publishes that commitment, identified by the DBC’s spend key (or a hash of the key), on the Safe Network before it makes a ReissueRequest . Each MintNode then only has to read the Spentbook entry for each DBC and validate that the entry is correctly signed by the DBC owner. This simplifies operations for the MintNode, which no longer needs to write any data, and keeps the MintNode’s reissue API idempotent. In other words, the Client can call reissue many times with the same ReissueRequest and always get the same response.

This is an amazing idea! The idea of clients publishing (probably in a special area of CRDT) their DBC transfers to manage spendbooks is amazing. I think this is a groundbreaking idea that only SN with asset transfer + storage function can implement. I like how the clients does most of the work and the nodes does some sort of routing. Because of this, SN looks like the internet to me. Thanks for SN Team, @danda & @dirvine

[danda]

credit where it’s due. This was @dirvine’s idea, and David Rusu has been implementing it. My contribution was only to write the above summary blurb and review some related pull requests.

[Secretariat415]

Thanks so much to the entire Maidsafe team for all of your hard work!

To all of the people who are wondering about the ultimate success of this project, yes, it is not a guarantee. However the integrity, transparency, and accountability of this organization, is unmatched.

Also, the honesty, friendliness, and knowledge sharing of our forum members is unmatched.

[anon23746431]

Thanks for the very easy pictures, a specific and easy explanation. @maidsafe .

[steve_smith]

DBC and Farming is same thing ? I am not sure, can someone please guide me?

[dirvine]

DBC is the token mechanism, how to transfer tokens between entities.

Farming or earning etc. is the service that users pay for with tokens. The mechanism from user paying to resource providers getting paid uses DBCs to make payments and the network identifying who to be paid for what work.

[Silent_Follower]

Thank you for the answers. Things are much more clear to me now.

MaidSafe is the great project with the great community

[steve_smith]

Thank you so much

[DeusNexus]

DBCs will really be a very essential part for the SafeNetwork and eventually be the next revolution in tokenizing anything!

[Vort]

@maidsafe

a node cannot choose which section it will be in

I thought that chosen section is derived from node’s key, which can be arbitrary.

Do section selection still works this way?
Or my understanding is not correct?

[dirvine]

@Vort

I thought that chosen section is derived from node’s key, which can be arbitrary.

As nodes age they need to create new keys for a new section, so in a range given to them. This means they cannot influence where they go as they age and when they age enough, they become Elders.

[Vort]

@dirvine

As nodes age they need to create new keys for a new section

Is new section always needed for Adult->Elder promotion?
What happens when Elder goes offline?
Adult from the same section or from different section replaces him?

[dirvine]

@Vort

What happens when Elder goes offline?
Adult from the same section or from different section replaces him?

The oldest Adult is promoted.

Also if a node relocates here and is older than youngest Elder then the youngest Elder is demoted and the new node promoted.