From looking through the sn_client code, I realise you can set a target XORURL for a sequence too. The CLI just passes a random XORURL, but the client is more flexible.
So, you could create an XORURL for the data you want to tokenize (PDF, mp3, image, etc), then use it as the input to generate a new XORURL, which you could use to store the NFT token (ledger/sequence). If you want a one-to-one mapping between data and token, this would seem a great way to do it. As you can create the XORURL for the data prior to upload, you can also create the NFT first, ensuring no one else can beat you to it.
If this (or similar) became a standard, it would be easy to derive whether an NFT existed for any XORURL. You could then derive the creator and the current owner easily. That seems pretty cool to me.
I agree. I think NFTs like $2M for Jack’s trivial first tweet is just over-hyped nonsense by people with so much money they don’t know what to do with it. Just my opinion and perhaps wrong because people ARE buying this stuff. If as an investment I think they are going to get burned badly.
On the other hand, if someone creates digital art they may be able to reach a wider audience and get some compensation this way. I.e. aside from the ridiculous examples, there could be many more reasonable uses that grow. I could imagine online art galleries (have seen some ads already) with reasonably priced material that people are buying in a less hype-driven manner.
In case some electricity black out and ongoing electricity issue for next couple days the one will try to reconnect soon as possible when electricity is on, the other will wait until it is clear, that the issue is solved. In the and the network will give only one penalty to one who was couple days off, while the other will lose all age.
Is it some way how to reduce this penalty?
The penalty will be the same (likely) for both nodes, they will both be relocated with a lower age (same reduction of 1). However if a node is off for a very long time then the network will forget him (at least at the moment) and he will start again.
I am not sure if I write it clearly.
The first node is many times on and off like this:
1st. day 20h off
2th. day 4h off
3rd. day 20min off
5th. day 20min off
The second node predict other outage and is waiting as long as he can to be not forgot by network.
While they both can not really predict if ISP provider or local energy grid collapse again.
The very long time to not exceed will be known for farmers ?
Could one farmers announce to network I am off for next xxx minutes, due planning maintenance to reduce penalty ?
It will be, well within bounds as it depends on how fast the network is changing. (it’s only humans that do time )
Possibly something we can do later, but we need to consider every edge case though. It likely will be OK, but the penalty is age - 1 and I am not sure we can reduce it much less than that really.
This reminds me - does a section have a counter? If not, could it? Perhaps it could be incremented periodically in response to network actions (node joining, node leaving, data mutation, data get, etc)?
I’m just thinking that it could serve as a ticker. It wouldn’t be a clock - heavens forbid - but it could be useful to know the sequence of operations. It wouldn’t need rely on system clocks or such, but if change X happened at 123456 and change Y happened at 123500, you would know X happened before Y.
Just wondering if such things have been considered. I’ve not got into the sn_node code yet to answer it myself!
Trying to not politically answer here. It does not have a clock, but there is a SectionChain so sections advance (Elders change) and this chain progresses. It may be an age between “ticks” but you can recodnise data was put on the network at SectionKey X for instance.
I am always a bit interested in “time” and “order of events” type things and wonder does it seem useful and almost automatic for us humans, but does it really matter? I mean the actual use case is hard for me to see.
Don’t get me wrong I hear the copyright claim stuff, first to invent and more but wonder does it really matter?
I digress, however, but yes there is an advancing logical clock with massively large resolution.
Maybe for compute/“smart contracts”? The SectionKey x < SectionKey y logic would be rather local to the section and it’s offsprings (section splits). But then a smart contract could use its state to track event order?
But that’s only if the system you’re seeing it through is proprietary & closed off. And the owner is allowing you, the “consumer”, to only use “certified” assets. In an open system you would be the owner of the space (like your house) and could just put a simple image to the wall. For games on the other side it’s understandable if the asset (like a weapon) is interacting with the game world.
If an artist wants to mark an image as “original” (as in “not modified”) a simple signature would suffice, no need for an NFT. But then you could copy it and it wouldn’t be “unique” anymore, so it’s rather a monetary and status symbol purpose.
I see potential for NFTs in the material world, for an easier decentralized management of resources. Like this (to some extent…):
Many of you heard about #NFT tokens & hype around them. A lot of things happening right now looks silly & we believe that real potential of #NFT is still unexplored.
To celebrate our new single on Eatbrain we decided to release NFT THAT HAS REAL VALUE.
The owner of token will get all artist’s income generated by “Ghosts / Final Boss” release in 2021. It means that winner of auction who will get token will get rights to claim & collect ALL ARTIST’s ROYALTIES we would normally earn from sales & streams (on Beatport, Spotify etc).
Not that useful or exclusive to NFTs, yet (they are going to just pay the “winner” some $ on their fiat account, i guess). But if NFTs take off and gain some traction this could result into real resources getting managed though NFTs.
)
- but it could be useful to know the sequence of operations. It wouldn’t need rely on system clocks or such, but if change X happened at 123456 and change Y happened at 123500, you would know X happened before Y.