1. 2

This might interest this crowd. I built a decentralized invite system with a Pachira Lottree for a cryptocurrency called Merit.

Just like lobste.rs and std.bz, Merit is invite only. There were many reasons behind this but some of them are

  1. Create a valuable identity on the blockchain.
  2. Reduce the rate at which bad actors can function in the system.
  3. Provide stable growth which can provide some price stability.
  4. Create a Lottery Tree system.
  5. Provide a diffusion of who holds new coins.

You can read the detailed technical parts in the bluepaper or read the code which is live now.

I will provide a summary here.

  1. Invites are created by miners and the amount is controlled via looking at growth using a moving average.
  2. Invites are distributed via a decentralized lottery.
  3. Users are incentivized to use their invites in a productive way via a Pachira Lottree, which defends against sybil attacks.

Besides this aspect Merit has some other features but I wanted to outline a feature that I think is very unique in the cryptocurrency space using some fairly new research into lottery trees. The effect on user growth seems to have been positive

  1.  

  2. 2

    Interesting! I perused the website and whitepaper and I love the idea of an adoption lottery to incentivize folks to invite their friends.

    One of the things I noticed you mention is the idea of decentralized recovery of your account. Is there a URL you could point me to that talks more about how that’s implemented?

    1. 2

      The lottery is not only to incentivize people to invite others. You can be part of the lottery without having to grow the network by staking. So you can also think of it as an “interest-bearing account” on the blockchain or a digital interest-bearing “bond”. The reason is your lottery score is based on the coin age of your wallet and your network. So if you don’t care about growing, you can still be part of the lottery.

      In regards to decentralized recovery, unfortunately, I need to expand on that more in the bluepaper. I don’t have a url but can explain it here.

      Merit has specialized opcodes (this is already implemented and live now) for building what we call Vaults. Vaults have two keys, a spend key, and a master key. The spend key is used to transfer funds out of the vault and is limited in certain ways like a whitelist of where it can spend and rate limiting. The master key can take the funds and change different parameters of the vault, including what the master key is.

      The idea behind decentralized recovery is to use a multisig opcode for the reset part where the creator of the vault only knows who must sign the vault reset. The rest is mostly a UI problem, but basically, the person would pick 3-5 people who don’t know each other as the signatories. They can then only require N-of-M signatures to reset the vault.

      If your master or spend key is lost or compromised, you can use your “guardians” to sign a reset transaction which allows you to change either or both keys.

      So it’s a way to recover and protect the vault without requiring a central third party.