Skip to content

Pixa's social marketplace V-DEV Requirements. [UPDATED] #319

@vipertechofficial

Description

@vipertechofficial

Hello everyone,

It looks like you guys achieved some good things regarding Vsystem and you know what? I've also done great on my pixel art editor which will be a NFTs Laboratory with Vsystem and everything it has to offer, look, we must with some associate of mine (to which I am still inclined to engage since 2-4 associate is what we need) envision to create a kind of Instagram yet being anonymous and hosting pixel art only (pixel art we can scale in intelligent shapes even in photo-realistic image with AI) so let me explain to you what we will have to use on Vsystem if we use it extensively okay?

  • A stable coin with possibility to buy it using Paypal or strip
  • A very simple exchange to buy Pixa's token back and forth
  • A system of NFTs contract which uses a reference to a V-DB entry which is pixel art in base 64 (1-16 kB seems good while being encoded in a simple string is ok)
  • A system that list NFTs for an address (created, sold and bought)
  • A system of linking information which can be updated for a address so we can create a profile system, which can be used to list NFTs too (simple as f*ck)
  • A system of private memo (things done in wallet.crypto.reed) and transaction (ideally something like ZK-snarks is appreciated)

Everything looks simple as of the current time we are breathing but hey, can we feed the DB like put "{{address}}/pixaprofile" or broadcast "{{address}}-pixaprofile" ??? Seems okay or not?

If there is missing func. we'll use trad. solutions instead while you get that s* running well in the JS SDK.

matias-affolter-localhost-8080-pixel-laptop-with-hidpi-screen-1
matias-affolter-localhost-8080-laptop-with-hidpi-screen-2

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions