Skip to content
This repository was archived by the owner on Jan 19, 2026. It is now read-only.
This repository was archived by the owner on Jan 19, 2026. It is now read-only.

Logical bug in the concept #7

@w1kke

Description

@w1kke

This concept does not work in my opinion as it has a logical flaw:
The process does in no way ensure that the team/person that was backed will later launch the service that they got the backing for on the platform.
And if they do there is no way to guarantee that the pricing will be in any way reasonable.

As the Foundation does not get a copy of the source code this cannot be ensured.

Possible solutions I can think of are:
1.) The team has to give a copy of their source code to the Foundation as a backup if they will not offer the service or discontinue to do so. The Foundation can then offer it based on the cost of the resources consumed.
2.) There is a KYC and a legal binding document that the backed team has to sign to get the backed tokens - although this has many many implications regarding international laws etc.

Regarding the cost of the service:
The solution will be benchmarked as another step and this will be determined as the baseline for the cost of the service.

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