[Worker Proposal] TUSC Worldwide Node Infrastructure 1 Year - iamredbar

Problem:

While being mostly reliable, TUSC currently has only two public API nodes (4 are listed in the reference UI, but two are unreachable at the time I am writing this). These two nodes are in the United States and Singapore.

Solution:

Plan and implement 5 API nodes worldwide in strategic positions to provide better worldwide network coverage for TUSC for 1 year.

Locations: Canada, United States, Germany, India, Australia

Location reasoning: Strengthen North American network while providing a wide area of coverage from Europe to the Oceania region (see image below)

Worker Pay:

Current price of TUSC at time of writing is $0.000007 / TUSC. This is roughly 142,857 TUSC / $1. These are the USD valuations I will use for the budget. See photo below for high level overview of costs, explanations below:

TUSC equivalency: $3003.95 @ 142857 TUSC / $1 = 429,135,285.15 TUSC, or 1,175,713.11 TUSC / day.

Line Items:

Server Implementation Hourly (Once) - this is a one time fee for implementation time of the servers. This includes setting up domains and SSL certificates for all 5 API nodes, as well as setting up monitoring. Also includes blockchain sync start, once the node is up and running it will convert into administration time. This will be paid out when all 5 API nodes are syncing to the blockchain and configured with proper DNS and monitoring.

Server Administration Hourly (Full Year) (Banked) - this is the estimated administration time for all nodes for a full year. Once the worker starts and the nodes have started their sync, the full 60 hours of banked time will start. This is not paid out immediately, rather as work is done throughout the year. Work that falls into this category will be billed in 15 minute increments and paid out at the end of the day the work was completed. If not all of the time is used at the end of the 365 day worker, the rest will be returned.

Monthly Server Cost (Full Year) - this is the cost of renting the hardware for the API nodes. These servers should be enough to sustain these nodes for a full year. This will be evaluated monthly and if upgrades are needed, the server administration fee can be rolled over into this category.

Monthly Server Monitoring (Full Year) - using the service UptimeRobot, we can have constant uptime monitoring with a webpage that the public can view if the service is up or not.

SSL Certificate - this is a one time cost that is needed to provide secure internet traffic to the nodes

Implementation:

I estimate that this infrastructure will take me 7 days to get running and ready for public consumption. After the nodes are synced, they will need to be added to the reference UI at wallet.tusc.network. They can also be used by the public for developing 3rd party applications as well.

Accountability:

Accountability is a big concern for these projects. I plan to keep everything transparent by posting all payouts in this thread and price evaluations at time of payout so that the community can keep track.


Let me know if anyone has any questions or concerns, I would be happy to chat.

Comments

  • Initial server implementation was completed earlier today. Due to the worker paying daily, the first line item will need to either be paid out when the balance accrues to be enough, or paid out in smaller portions. I will likely withdraw it in 20% increments as the vesting balance increases.

    The SSL certificate has been purchased and so has the first month of monitoring. The monthly server fees are post-pay.

    SSL Cert - $19.95, TUSC current value = $0.000007, $19.95 = 2,849,997.15 TUSC

    Monitoring - $7, TUSC current value = $0.000007, $7 = 999,999 TUSC

    Total of first withdrawal: 3,849,996.15 TUSC

    There is a 1 week vesting period before I can withdraw any funds on the worker. This is when I will make the first withdraw and update this post again.

  • Today I withdrew 19,010,388.41889 TUSC from the worker.

    I was charged two smaller charges for the month for the server hardware, as it was started late in the month. This total came to $18.25.

    The price of TUSC has changed since the worker has started, but I will respect the prior TUSC amount for the above payout. I will subtract the 3,849,996.15 TUSC from the current withdrawal before paying out more. This leaves 15,160,392.26889 TUSC for other payouts. Current TUSC value: $0.000005.

    The remaining withdrawal will go to server implementation costs. 15,160,392.26889 TUSC = $75.80

    UNPAID:

    • Dec Server - $0 / $18.25
    • Server Implementation - $75.80 / $500

    PAID:

    • SSL Cert
    • Dec Monitoring

    Once I withdraw again I will evaluate current TUSC price when paying out the unpaid balances.

  • 3,908,610.37030 TUSC claimed from worker pay.

    Current TUSC value: $0.000005

    USD value: $19.54, paying all Dec Server fees and putting the rest to implementation.

    UNPAID:

    • Server Implementation - $77.09 / $500

    PAID:

    • Dec Server
    • SSL Cert
    • Dec Monitoring
  • 18,094,756.92591 TUSC claimed from worker pay.

    Curent TUSC value: $0.00000454

    USD value: $82.15, was charged $7 for January monitoring. Paying January monitoring and putting the rest into implementation pay.

    UNPAID:

    • Server Implementation - $152.24 / $500

    PAID:

    • Dec Server
    • SSL Cert
    • Dec Monitoring
    • Jan Monitoring


  • I performed 1 hour of maintenance to the nodes. No pay to cash out currently, so it will be put on the docket of unpaid.

    UNPAID:

    • Maintenance - 1/60 - $30
    • Server Implementation - $152.24 / $500

    PAID:

    • Dec Server
    • SSL Cert
    • Dec Monitoring
    • Jan Monitoring


  • I was charged $50 for January server hardware on 2/1.

    I claimed 9,183,445.38229 TUSC from the worker on 2/6. Current TUSC value is $0.00000457. This equals approximately $41.97.

    UNPAID:

    • Jan Server - $11.97/$50
    • Server Implementation - $152.24 / $500

    PAID:

    • Maintenance - 1/60
    • Dec Server
    • SSL Cert
    • Dec Monitoring
    • Jan Monitoring


Sign In or Register to comment.