CirclesUBI has historically been built on a “central virtual server” (the blockchain acting much like a single virtual server but it is distributed as many validators replicate it). CirclesUBI could also be built in a decentralized way where each person (with their “person coin”) has their own ledger. In such an implementation, there is an attack vector known as the “reserve payment attack”. All decentralized multihop payment systems have problems with this attack vector, it has never been fully solved - until now. I solved it this spring, with a 3-phase commit (rather than the 2-phase commits people have used historically). So now it is possible to build CirclesUBI in a decentralized way. I present the solution in Austria a few months go, https://youtu.be/DVjMis02AE8. Below is a schematic, and a simple overview is on https://ripple.archi/3phase.pdf. My Resilience (that does web-of-trust basic income via transaction tax rather than taxing the transaction volume as AlexJC’s “Flow” suggested in 2014 and CirclesUBI has done since 2015) has been implemented with the 3-phase commit already, see Bitbucket (or Bitbucket for a C version although I have not added swarm redistribution to that yet, but doing so is just a days work). /Johan
