Hacker News new | ask | show | jobs
by asciimike 1626 days ago
I see that CSVCHAIN is "held in cold storage on this USB drive" a 1 GB thumb drive. This seems to imply an upper bound on the number of NFTs on CSVCHAIN. How, I wonder, does the creator of this project expect to scale CSVCHAIN beyond this limit?

Additionally, can we secure guarantees that the project owner is safely ejecting the USB drive in question?

2 comments

Once Roy makes some $ he could horizontally scale to a 2GB drive. Or 2 1GB drives and keep one in his sock draw so it's distributed in his house.
In the event of using 2 1GB drives with one stored in the sock drawer, how do we prevent the quite literal "evil maid" attacks altering the CSVCHAIN?

Additionally, if we do use this mechanism, I petition to fork the name from CSVCHAIN to SockChain.

I don't know how many times I need to repeat this FACT on this site, but socks are NOT immutable. How many holes do you have in your 7 year old socks? I'd wager a LOT. How many mismatched socks do you have in your drawer? I'd wager, AGAIN, a LOT.

The only way to make this truly secure, is to have 2 USB thumb drives, plugged into a different side of the machine (god hope you have a machine with USB ports on both sides). Then, saw the machine in half, right down the middle. I'll find the crypto paper where I read about that.

One of the most fascinating things I learned as a kid is that you can cut a Planaria flatworm in half, and each half regenerates the missing half. So now you have two Planaria.

If this works for the CSVCHAIN PC, you could have exponentially increasing compute power and storage!

Regarding the socks, a good trick is to use two drawers. One drawer has only matched pairs of socks. Unmatched single socks go in the second drawer, and some of them will eventually find a matching sock.

I plan to write an article on this. I will call it Socks and the Singles Drawer.

Alternatively, only buy socks that are identical. That way any two socks are already a pair. This entails 50% fewer drawers.
Socks are in fact immutable infrastructure. When your EC2 instance crashes, you shut it down and provision a new one. When your socks get holes, you throw them out and buy new ones. This isn't 2010 anymore, you really think people debug their servers and mend their socks?
You are thinking about threads, not socks. It's the threading technology you need to review; HINT: the color matters.
The threads built on NFT-w (natural fibre textile, wool) don't have these issues and can be spun up in a more eco-friendly way. All these garment-haters that talk about how cotton requires huge amounts of land and water don't seem to understand that we have already solved these issues by using a BAT (basic ALPACA token), and those of us who bought BAT early will be riding this kid all the way to new zeeland!

EDIT: the downvoters are just people who don't know how a POW (proof of wool) exchange works, or are in denial about how we can scale it by using clumps to have localized, bidirectional hair-pulls. It can scale from dual-crimps all the way up to a felt.

Socks are cattle, not pets
Only up to a certain age. Once you pass 50 or take up hiking, you start buying serious pet socks. Merino wool triple layer moisture wicking tough heel socks? Shut up and take my money, REI!
A lot of people haven't worked with socks beyond the level of Winsock.
When the first drive fills, take the hash of the file, and make it the first line of drive two. That way they are chained together.
> he could horizontally scale to a 2GB drive

Minor nitpick: I believe you wanted to write "vertically scale".

I think sharding to multiple drives would be more decentralised.
I wish I could upvote this more
This should be possible using "split" technology: https://www.gnu.org/software/coreutils/manual/html_node/spli...