Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CSVCHAIN - NFTs backed by CSV technology

csvchain.com

Post reply on HN
Print view View original

151–160 of 171 posts

Re: CSVCHAIN - NFTs backed by CSV technology

#151

Post by Spivak »

miracle2k wrote: post #59
NikolaNovak wrote: post #41

Earlier quoted context omitted.

My current way to explain to non techies is that it's like those "Name a star" sales: * Artificial seeming scarcity out of something that's inherently abundant * No actual ownership of actual thing * Instead, a overly-detailed focus on mechanics of the process: We will send you a gilded certificate; we will put your entry into a leather bound book; this cook will be registered with United States Copyright Office; it…

There is another critical difference: The person creating the NFT is, in theory, the artist who as a claim to authorship of the work.

True, its more like an artist assigned numbers to all their works and sold the right to put your name on a website next to that number. Maybe for some artists that means something like getting a shoutout on their Patreon but totally worthless in abstract.

Re: CSVCHAIN - NFTs backed by CSV technology

#152

Post by Zambyte »

yucky wrote: post #132
Zambyte wrote: post #128

Earlier quoted context omitted.

This is not a good metaphor for NFTs. The content of any NFT can be perfectly duplicated by anyone. The only part of an NFT that matters is the signature. A better analogy would be musicians signing CDs / vinyls, sports players signing player cards / equipment, etc. People buying NFTs created by nobodies are simply getting scammed. The physical metaphor here would be like paying a random amateur sports player to sign…

I don't think this is the case with unlockable NFT's, is it? You can copy the "box" so to speak, but you can't see what's inside if you don't own it.

I have not followed NFTs like this very closely, but my understanding of them is this:

* There is some contract that generates NFTs under some condition (this is the box you mentioned)

* When the condition is met to create a new NFT, it creates one using VRF data, similar to how is described here: https://blog.coincodecap.com/how-to-generate-random-numbers-...

Anyone can make an NFT and stuff the same random number(s) into it that the contract received from the VRF. The difference is in who made thr NFT. Most people wouldn't find an NFT interesting if it's just a random number, made by a random person. An NFT which was produced by a smart contract might be exactly the same, but it is more interesting because some (usually centralized) game or service uses that random number to represent something else. That game or service is only interested in NFTs created by their smart contract.

Re: CSVCHAIN - NFTs backed by CSV technology

#153

Post by joshu »

Stratoscope wrote: post #90
xrd wrote: post #71

Earlier quoted context omitted.

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…

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…

Alternatively, only buy socks that are identical. That way any two socks are already a pair. This entails 50% fewer drawers.

Re: CSVCHAIN - NFTs backed by CSV technology

#154

Post by kjellsbells »

jeofken wrote: post #131
howdydoo wrote: post #75

Earlier quoted context omitted.

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?

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!

Re: CSVCHAIN - NFTs backed by CSV technology

#158

Post by seanhunter »

weego wrote: post #63
asciimike wrote: post #62

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?

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.

I think sharding to multiple drives would be more decentralised.

Re: CSVCHAIN - NFTs backed by CSV technology

#159

Post by ryan_lane »

mpyne wrote: post #146
mwattsun wrote: post #83

Where's the smart contract capability? Smart contracts are important in certain applications, which is why I store purchases in XML and do transformative contracts in XSLT. Version 2.0 of XSLT is Turing-Complete, with the added advantage that XSLT syntax is a specialized form of XML, so I only have to use one syntax for coins and contracts. I call mine Dotcom Bubble Chain.

> I call mine Dotcom Bubble Chain. It may or may not surprise you to find out that the U.S. Navy came ->this 2018 , so that we could use XSLT and other XML technologies so that they could "Enable maximum use of commercial products built to this standard", "Improve cybersecurity at the data element layer by using the XML Security Assertion Markup Language (SAML) protocol", and "Enable compression of data using the XML…

Nah, they've been at that since at least 2005, when I worked there, and I'm pretty sure it was in their guidelines for years at that point. My guess is that they still have that in their guidelines.

For the most part, when doing a procurement, you'd just check a box that the software supported XML in some form (and many vendors added some stupid XML feature, even if their software didn't have a need for it at all), and it would satisfy that requirement.

Re: CSVCHAIN - NFTs backed by CSV technology

#160

Post by davidgerard »

mwattsun wrote: post #150
mpyne wrote: post #146

Earlier quoted context omitted.

> I call mine Dotcom Bubble Chain. It may or may not surprise you to find out that the U.S. Navy came ->this 2018 , so that we could use XSLT and other XML technologies so that they could "Enable maximum use of commercial products built to this standard", "Improve cybersecurity at the data element layer by using the XML Security Assertion Markup Language (SAML) protocol", and "Enable compression of data using the XML…

> in 2018 That's quite a lag. Peak XML was probably 2000 if I recall correctly. That said, XSLT is pretty cool from a language standpoint. I wouldn't want to program in it all day anymore than I'd want to program all day in Brainfuck, but you have to admire the weirdness of it.

have coded actual XSLT, I assure you that Turing completeness is a curse
Post reply on HN