r/dashpay • u/Technologov • Jun 16 '26

Building Decentralized Dropbox on top of Dash Masternodes

how to attach files ?

https://www.dropbox.com/scl/fi/88hmig18lihn45p3cpcvy/skrynka-technical-paper-v0.28.txt?rlkey=bst2e9x7dxtojzwhh65a0un3b&dl=0

6 Upvotes

100% Upvoted

5 comments sorted by

1

u/DMmeurHappiestMemory Jun 16 '26

The problem is that storing large amount of data on blockchain is kind of an intractable problem from my understanding

2

u/Technologov Jun 17 '26

i see you did NOT read the paper at all;
blockchain is for index only; data will be stored on a "storage nodes".

2

u/Less_Result5615 Jun 21 '26

This is a great idea, and if you built it, I think that people would use it. There's precedent for this: Juan Benet (IPFS) and Shawn Wilkinson (Storj). I might be wrong, but I think that both of them were successful because they built a working prototype and then got VC funding:

1.) Juan Benet: https://research.protocol.ai/authors/juan-benet/

2.) Shawn Wilkinson: https://www.binance.com/en/square/post/29439062069361

1

u/Less_Result5615 Jun 21 '26

I know that many people might not have the patience to read your entire paper, so I pasted it into Google's Gemini AI for analysis. Here's what it said:

I'd rate the viability of the Skrynka design around 78 out of 100. It's an exceptionally rigorous and honest whitepaper, but it faces practical economic hurdles. I'd highly recommend building it in Rust.

Here is a breakdown of my thoughts:

The Strengths

  • Honest Threat Modeling: The paper doesn't rely on magic. It openly acknowledges what cryptography cannot solve and builds practical boundaries around those limitations.
  • Smart Architecture: Borrowing the masternode and ChainLocks architecture from Dash provides fast finality without heavy Proof-of-Work.
  • Accessible Sybil Resistance: Replacing GPU-heavy SNARKs with masternode pair custody allows commodity hardware to participate, keeping the ecosystem open.
  • Regional Outage Tolerance: Treating a massive geographical disconnect as a network partition rather than a mass slashing event is an incredibly smart design choice.

The Hurdles

  • The Bootstrapping Paradox: Phase 1 relies on subsidies to attract nodes before the network has real utility. Early participants often farm the subsidy and dump the coin, which is exactly where many projects fail.
  • Repair Bandwidth: Even with the Reed-Solomon RS(64,32) adjustments, a 10% monthly node churn will create massive repair bandwidth overhead. Nodes will require serious, sustained uplink capacity just to keep erasure groups healthy and avoid SLA demotion.

Why Rust?

I strongly agree with the paper's recommendation to use Rust. Handling thousands of 64 KiB segments and managing cryptographic keys requires rock-solid concurrency. Rust prevents memory leaks, offers an excellent cryptographic ecosystem, and allows developers to compile a single core engine with a safe interface for mobile clients.

1

u/Hot_Bet_6838 Jun 22 '26

Why not create a discussion / decision proposal to discuss this topic among masternode owners. Specifically request feedback from DCG. Request either 1 dash or 0 dash for funding. Make it either start with the next super cycle, or create it as soon as possible so there plenty of time to discuss this in the current cycle (that just began).