Skip to content
This repository was archived by the owner on Feb 13, 2023. It is now read-only.
This repository was archived by the owner on Feb 13, 2023. It is now read-only.

Tampering by whom? #5

Open
Open

Description

@dominictarr

It's not clear what sort of tampering you are talking about in section 3.4.3:

BitSwap nodes keep ledgers accounting the transfers with other nodes. This allows nodes to keep track of history and avoid tampering

To be honest, this seems like a very important section of the paper, if not the most important, but it's unclear why a rational peer wouldn't loose their ledger.

When activating a connection, BitSwap nodes exchange their ledger information. If it does not match exactly, the ledger is reinitialized from scratch, losing the accrued credit or debt. It is possible for malicious nodes to purposefully "lose" the Ledger, hoping to erase debts.

Activity

  1. jbenet commented on Jun 26, 2015

    @jbenet
    Member

    bitswap is notoriously underspecified in DRAFT 3. DRAFT 4 will do better.

    To be honest, this seems like a very important section of the paper, if not the most important, but it's unclear why a rational peer wouldn't loose their ledger.

    this is a feature, like any other. A peer repeatedly losing a ledger erodes trust. with all of these what you want is the nodes to be free to measure whatever parts of the interaction they deep relevant and decide trustworthiness themselves. goal is to ship an ok base case and a few interesting choices

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions