RE: NFT Research - Creation and Distribution

[disregardfiat]

• This is an NFT of an image, but it's not limited to images at all.
• DLUX runs on an opensource code base that can be used to build any community that has enough computer and HP resources, these open source modules to compute NFTs will be portable between them.
• This NFT is DRM. Point to the API of any node running the layer 2 code base and query an NFT to find its definition and owner. Or query an account to see who owns what.
• We'll likely have our own DRM like image server /api/user/profilepic where PeakD or any site that wants to can put a blue check next to a profile picture. This is why having a script that runs on server and in browser are so important. Especially for things like DRM, where PeakD might have a token to generate these profile pictures where rando user can not(save resources as well).

Comments

[simplegame]

Thank you for the clarification.
Super exciting.

Do you have the node API's defined yet?
Sorry I have not read through the docs yet. Just doing some info gathering.

[disregardfiat]

We're still trying to see what is needed between the front and backends, but we have some dummy data coming from only at token.dlux.io to help us build

api.get('/api/nfts/:user', API.nfts);
api.get('/api/nft/:item', API.item);
api.get('/api/sets', API.sets);
api.get('/api/set/:set', API.set);
api.get('/api/auctions', API.auctions);
api.get('/api/sales', API.sales);

Would appreciate your input

[cryptosharon]

When will your API be live for coders to play with?

[disregardfiat]

There is dummy data live right now, trying to see what all we need to make a front end work. You're welcome to play with it... especially if you drop in our discord server and give us feedback.

api.get('/api/nfts/:user', API.nfts);
api.get('/api/nft/:item', API.item);
api.get('/api/sets', API.sets);
api.get('/api/set/:set', API.set);
api.get('/api/auctions', API.auctions);
api.get('/api/sales', API.sales);

From token.dlux.io or if you run the 'defi' branch of dlux node software

The API will have live data when we make our announcement post.

Here is our working generate NFT client side script.

fetch(`https://ipfs.io/ipfs/${nft.script}`)
      .then((response) => response.text())
      .then((data) => {
        const code = `(//${data}\n)("${nft.uid}")`;
        const SVG = eval(code);
        document.getElementById(`image-${nft.set}-${nft.uid}`)!.innerHTML = SVG;
      });

[keys-defender]

@disregardfiat Your comment contains some text that could be a potential attempt to inject malicious code. cc: @cryptosharon

Investigation in progress..

Please forgive any false positives.
More info: _{https://hive.blog/hive-139531/@keys-defender/new-feature-code-injections-attempts-detection-xss-sql-injections-csrf
Comment 1% downvoted to make it less visible. This message is self-voted to be more visible among others.}

@keys-defender

[cryptosharon]

it's not 🤣🤣🤣🤣🤣

[keys-defender]

Good! 😊 🤖

[cryptosharon]

do you have a sample fetch to upload to ipfs.io?

[disregardfiat]

https://dlux-vr.glitch.me/build.html is where a whole bunch of that type of code lives... https://glitch.com/edit/#!/dlux-vr?path=public%2Fimg.html%3A10%3A0 is the Save to IPFS fucntion

[cryptosharon]

thaaaank you! 😊😊

[cryptosharon]

how much time is estimated till your announcement post?

[disregardfiat]

2-3 days hopefully. Even if the API is live at that point it will still be under development while we test features

[lordbutterfly]

@peakd Guys, this is definitely something to work into the platform.