Create payments via Lightning/BTC

[otech47]

In addition to being able to add payments directly into Trinary via a form, we want to be able to connect a Lightning invoice / BTC transaction ID to the payment

The core purpose is to integrate Trinary with a real live mainnet BTC full node that can receive payments

[otech47]

Should we add a Lightning invoice generator on this page?

[otech47]

https://btcpayserver.setlife.tech/docs

[otech47]

Add guest user [email protected] with password @otech47

[otech47]

Onboarding Trinary Contributors to the Bitcoin network via Lightning

• Voltage.cloud nodes for all contributors
• Trinary node send live payment withdrawal requests to contributors claimable by any LN compatible wallet
• Contributors download Zeus mobile wallet + configure Voltage credentials (or connect their own node) to receive payments from Trinary node

~$13 / contributor per month fixed cost
~$X fixed amount tips from Trinary node (max monthly budget)
Derive X from 6-month term contracts (must match $ cash + fixed sats on hand)

[otech47]

Client-Contributor Engagement

1. A Client (Alice) who is willing to make a Payment at a later date seeks a Contributor (Bob) who can provide some proof of a deliverable such as a software package, UI designs, technical specs, etc

Consider the following data query structure

client(id: 1 ) {
  id
  name
  payments: {
    amount,
    date_incurred,
    date_paid,
  }
  projects: {
    name
    allocations: {
        amount
        rateDetails
        contributor: {
            githubUrl
        }
        payment: {
            amount
            date_incurred
            date_paid
        }
    }
  }
}

---

2. Alice creates both the project and the payment

Client
{
    id: 1,
    name: 'Alice',
    payments: [{
        amount: '2,000,000 sats',
        date_incurred: '2022-01-01',
        date_paid: '2022-01-02',
        amountNotAllocated: '2,000,000 sats'
    }]
    projects: [{
        name: 'Project A',
        allocations: [],
    }]
}

---

3. Alice creates an Allocation for the new Project assigning herself as the 1st Contributor. The hourly rate, expected hours, and total
   expected payment is transparent for all other Contributors to see

Client
{
    id: 1,
    name: 'Alice',
    payments: [{
        amount: '2,000,000 sats',
        date_incurred: '2022-01-01',
        date_paid: '2022-01-02',
        amountNotAllocated: '1,000,000 sats'
    }]
    projects: [{
        name: 'Project A',
        allocations: [{
            amount: '1,000,000 sats',
            rateDetails: '40 hours @ 25k sats/hr',
            contributor: {
              githubUrl: 'github.com/alice'
            }
            payment: {
              amount: '2,000,000 sats',
              date_incurred: '2022-01-01',
              date_paid: '2022-01-02',
              amountNotAllocated: '1,000,000 sats'
            },
        }],
    }]
}

---

4. Alice creates an Allocation for the same Project but proposed to Bob assigned as the 2nd Contributor with payment terms

Client
{
    id: 1,
    name: 'Alice',
    payments: [{
        amount: '2,000,000 sats',
        date_incurred: '2022-01-01',
        date_paid: '2022-01-02',
        amountNotAllocated: '1,000,000 sats'
    }]
    projects: [{
        name: 'Project A',
        allocations: [
          {
            amount: '1,000,000 sats',
            rateDetails: '40 hours @ 25k sats/hr',
            contributor: {
              githubUrl: 'github.com/alice'
            }
            payment: {
              amount: '2,000,000 sats',
              date_incurred: '2022-01-01',
              date_paid: '2022-01-02',
              amountNotAllocated: '1,000,000 sats'
            },
          },
          {
            amount: '500,000 sats',
            rateDetails: '20 hours @ 25k sats/hr',
            contributor: {
              githubUrl: 'github.com/bob'
            }
            payment: null,
          }
      ],
    }]
}

---

5. Bob can then proceed and start working on providing a Deliverable trusting that Alice will create a Payment and link it with the proposed Allocation

Client
{
    id: 1,
    name: 'Alice',
    payments: [{
        amount: '2,000,000 sats',
        date_incurred: '2022-01-01',
        date_paid: '2022-01-02',
        amountNotAllocated: '500,000 sats'
    }]
    projects: [{
        name: 'Project A',
        allocations: [
          {
            amount: '1,000,000 sats',
            rateDetails: '40 hours @ 25k sats/hr',
            contributor: {
              githubUrl: 'github.com/alice'
            }
            payment: {
              amount: '2,000,000 sats',
              date_incurred: '2022-01-01',
              date_paid: '2022-01-02',
              amountNotAllocated: '500,000 sats'
            },
          {
            amount: '500,000 sats',
            rateDetails: '20 hours @ 25k sats/hr',
            contributor: {
              githubUrl: 'github.com/bob'
            }
            payment: {
              amount: '2,000,000 sats',
              date_incurred: '2022-01-01',
              date_paid: '2022-01-02',
              amountNotAllocated: '500,000 sats'
            },
          }
      ],
    }]
}

[otech47]

Voltage

1. /node/create is called when a client creates a payment in sats and creates at least 1 Allocation. /node/create is called again when a contributor has at least 1 funded allocation (these might be manually triggered via a UI)
2. /node/start is called on all nodes

[otech47]

Alby might be useful here too