Giter Club home page Giter Club logo

Comments (5)

ana0 avatar ana0 commented on July 24, 2024 2

Some notes: @saraswathi and I talked this through, focusing on usability concerns. We arrived a preference for option 3, with the actual trust limit amount being recommended offchain by something like option 1. The user could still have the freedom to override the recommended amount if they wanted.

This does lead to a problem where Alice trusted Bob early on, when they didn't have a strongly overlapping trust graph, but overtime as more mutual friends joined Circles, the trust limit should probably be updated. Could be helped by adding an offchain feature that checks for significant changes to trust network overlap and prompts Alice to update the onchain trust limit. Could even be framed as a reward, ie "Achievement unlocked! Your trust network with Bob is really strong - do you want to update your trade limit?" etc

Still needs final decision

from circles-contracts.

innsmouthrain avatar innsmouthrain commented on July 24, 2024

I think trust limits should have a very basic implementation because we should focus on leaving the personal currency step quickly, heading for community currency.

I don't think personal currencies can scale well and it's dangerous for us to try to treat them as if they would. They are a sybil defense for bootstrapping and a decentralized fallback in case of corruption or dysfunction on higher levels.

Limits to trust should exist to allow risk mitigation for new personal trust connections in case they are sybils or because they will use up all your own coins through transitive exchange. If it does these things I think it's finished.

Worrying about discrimination at this level I think is misdirected, intsead we should treat personal currencies as purely a sybil defense mechanism and hurry up and reach community currency territory, where scaling is much easier (and discrimination doesn't happen in this way).

from circles-contracts.

edzillion avatar edzillion commented on July 24, 2024

I think trust limits should have a very basic implementation because we should focus on leaving the personal currency step quickly, heading for community currency.

...

I disagree entirely, and I am guessing that this opinion would be controversial with the wider group as I haven't heard it articulated before.

Simply put, I am very wary of group currencies in general as I think we might end up recreating the system we are trying to replace (e.g. one money to rule them all and boo to anyone who can't or won't take part)

from circles-contracts.

ana0 avatar ana0 commented on July 24, 2024

Trying to summarize the existing proposals for managing trust limits ... There seems to be some consensus that trust needs to be limited. The question is how?

There are three main ways to do so that I see being presented.

  1. Suggested by Köppelman: The amount of tokens tradable with any other person is limited by the subset of overlapping trust connections they share. eg. If they share 1/2 their trust connections, they will never exchange tokens in such a way where more than half their total tokens are from that person.

  2. Suggested by Ed: The amount of tokens tradable decays with each hop of a transitive transaction. eg. A one-hop transaction can trade 100% of their tokens, but a the second hop decays by n and can only be at most 100*n%

  3. Suggested by Andy (I think?): Users set a trust-limit with each connection (and maybe this is recommended offchain in some way) and there's also a system wide epoch parameter. The trust limit is that maximum amount a user can exchange along that trust connection per epoch. eg. A user can transfer x CRC to another user per day.

from circles-contracts.

ana0 avatar ana0 commented on July 24, 2024

Closing, we have decided to use percentage of totalsupply as the trust limit parameter, and to recommend a flat rate system wide for the MVP

from circles-contracts.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.