Yes I think that was the idea, to have a moderated place that’s accessible by everyone. That proved to work if we manage to keep the set of moderators small I guess. Individual initiatives will still spawn into isolated groups to focus on stuff, but the overall discussion could remain visible
I’ll notify everyone in the existing dev groups about this thread.
@romeo Im not a dev.
Thanks, would be great to have access and see how we can connect all the dots and build something together.
Thanks
1 Like
I think it doesn’t matter if you’re a dev. Important is the motivation to move us forward. Once we go from small isolated contributions to coordinated efforts, we’ll need people skilled in other areas anyway, that help with coordination, planning, task scheduling, ideas, testing, recruiting, you name it. I think helping with that is also one of the long term goals of @dom_qsr and his az application.
2 Likes
@Dumeril agree.
So shall we focus on building?
Can you tag here few devs and lets map which tasks can be done? If they are hands on or prefer to be team leaders? we can hire devs globally if needed.
Tbh I don’t know who’s here already. Randomly remember seeing @georgezgeorgez, @CryptoFish, @vilkris in the member list, but there’s also quite a few names I’ve never seen before, so maybe some don’t have the same as in telegram.
I posted a message in both telegram dev chats though, linking this thread.
I want to refer you to this thread though https://forum2.zenon.org/t/what-are-the-communities-priorities-for-accelerator-z-and-hyperspace/233,
which includes some discussions about why I and others think that it’s important to get some transparency into the existing and planned work of the core team first.
Basically, we are on the verge of repeating tasks that maybe have already been or are being done.
E.g. we shouldn’t just implement a wasm vm because kaine said so, but if there’s existing r&d and he not just pulled that idea out of his sleeve, it is questionable if we should start over again in an information vacuum, iykwim.
Just read it thanks.
It seems a bit messy where better to start.
https://forum2.zenon.org/uploads/default/original/1X/c8f618d6edccc72491c55e2ec9648b67c98fa33a.jpeg
Based on this chart, Ill break it as I familiar with:
Bridges - can be great, but I dont see the value as long as we dont have our own ecosystem, DEX etc’. Having more bridges to different layer 1 means managing more liquidity in different pools and DEXes, who will provide it? who secure it with lock? I think BSC is more than enough at this stage.
BTC Inter. - is it doable at this stage? DEFI on Bitcoin is a big buzzword. I dont think it can be done at this stage.
Wallets - having an explorer wallet Metamask/Terra Station style can be a great product and sounds doable.
CEX - Being traded in low level CEX is it a priority? there is much better volume in PCS. Tier 1, 2, 3 CEX required MM, high liquidity, KYC, contracts - who will take care of it? This is not something the community can manage by its own. I dont think Zenon in a position to be traded in Tier 1, 2, 3 CEX based on its volume, reputation, current stage.
NFT Platform - as far as I understand not doable due to SC matters.
ZTS Platform - to create tokens? can be done easily in the wallet isnt?
Wiki/Gitbook - can be great tasks for the community.
Competition - not clear to me what it means
Marketing - always good to have. Paying for marketing is easy, just need to focus and set goals for it.
Branding - same as marketing above.
Satelite - no idea what it means.
Some of the ideas above, can be done easily without the team’s efforts. Regards development of VM, we would need more info from the core team in terms of r&d before starting it.
2 Likes
I agree on mostly everything. Some comments:
-
btc interop is doable in several ways according to kaine. There have been many discussions on telegram about that, don’t know if it’s summarized somewhere yet.
-
Browser wallets is being worked on by at least one group since the last initiative (warpdrive) @pdfust on telegram I think, he’s not here apparently
-
Our ZTS tokens don’t provide any value apart from being collectibles maybe or symbols of some sort. Probably something beyond that was meant here; same problem you identified for nft in that case
-
we have a great wiki and it’s being worked on actively currently
-
competition; also not sure, maybe meant to provide insights regarding Zenon compared to other l1
-
marketing and branding is also an ongoing effort in at least one dedicated telegram group. Maybe the current state could be described as trying to settle on recognizable identity and appearance.
-
early on Zenon proposed to develop satellites, but it was never clear what exactly that meant. Did they actually plan to start physical satellites to serve the network? Not unheard of. Could have also been a placeholder term for some network component that fitted their symbolism. They had announced a satellite sdk to be coming for NoM, so I think it was just symbolic. Satellites are the apps interacting with nom via the sdk.
Yea our discussion focused on vm’s a bit prematurely as this was the simple answer to your initial question. Maybe it was a stupid answer when followed up by the observation that it probably makes no sense to work on that in this exact moment. Sorry.
But summarized, there’s a lot of possibilities to lay the groundwork for future applications I guess. Everything that’s interacting with the network via existing sdks can potentially be expanded later on, when those sdks provide means to interact with smart contracts. Infrastructure projects, like the “projects” application that don’t need smart contracts but can grow into immensely useful platforms.
Even projects that actually require smart contracts, like the “Milky Way” nft application are possible in limited ways, provided you make sure you understand the current limitations and where you have to have placeholders for now.
2 Likes
I’ve only been following all the talk on the side line. I realise I simply don’t have the time to activly participate in all the discussions. That said however I do would like to participate and help out. I see myself working on a SDK , bug fixes or being part of team. I guess I’m waiting for someone to assemble a Team in which I can participate. Not interested in getting paid, but more for the learning experience etc.
4 Likes
This is exactly how this project will win. First slowly then quickly!!!
@CryptoFish Dumeril is working on a couple of SDKs, check out the Dev category for a list I’m putting together for this
1 Like
From the new NFT article:
-
Virtual Hologram implementation: minting should automatically insert the Virtual Hologram using a steganographic method
-
Spectral Attestation implementation: extract the Virtual Hologram and validate it using on-chain data
-
s y r i u s and other compatible wallets should support registering and transferring NFTs with multiple formats. For example, the s y r i u s wallet should support a simple and intuitive Drag & Drop functionality to mint an NFT or a collection of NFTs
What actual steps or development activities can we extrapolate out of these points?
1 Like
One first step would be to actually define a standard.
If you want to embed data and go by the idea of the article (it mentions things like smart contracts, hd videos) you have to agree what kind of data you want to allow as nft’d object. Then you have to check what kind of data you are able to embed there and how that would be realized from a technical standpoint. Then you would have to decide; do you want to allow one basic set of embeddable data? That would mean you agree on a subset that is supported by all data types you want to allow to be nft’d. E.g. embedding a hd video in a jpeg won’t be possible I guess for physical reasons.
Else you could say that only certain types are compatible with each other.
In parallel another group could look at how token minting can be realized, how the insertion of holographic data would work and how this data later would be validated.
With both tasks finished you could begin to define the minting standard, which would have to incorporate the results from both groups, so that a link exists between the minting and the insertion of data. Both steps are meaningless without the other.
Hopefully that wouldn’t require a change to the network code or even smart contracts. I think it would, as no standard is meaningful when it’s not validated somewhere, and that is probably not a task that should be left to the wallet builder. If it wouldn’t, at that point you could begin to implement the standard on syrius or elsewhere.
That’s a very rough description of the process as I would see it now.
2 Likes
so it seems a WASM SC mechanism is paramount on all fronts. In your opinion @devs is this achievable with a small group? Do we need to look more broadly for developers to assist with this or bring certain key skillsets in?
ETH is heading the WASM route too
Most of these devs are on LinkedIn and could be contacted outside of the Firm Hire organizations
what skills are needed exactly though? All it would take is getting one of them interested to potentially get the ball rolling
I’m spamming this thread, but I guess one key thing is can we write a job description/proposal similar to the below and start asking around?
You’re thinking about an az application that allows you to fund external devs, or what is the idea here? From a purely practical standpoint.
Try to gauge interest first, see if we can get any of them to bite.
Then funding wise, yeah we could have ~25k at current price to fund a Dev - would that be enough though? Even if it were to work as part of a team with yourself or others, if we could break down the work into smaller deliverables it could work well
We could front up money to start via community donations I’m sure of it
1 Like
Good, simple explanation of WASM
Ok I have two thoughts on that.
First is that I don’t think that you can hier external devs with znn at this point; so we don’t necessarily would have to pay everything upfront but it would have to be dollars or something easily convertible.
Second is that I don’t oppose the idea of outsourcing implementation, but I would prefer the community / us to define and specify the outcome we want to see.
So my suggestion would be to keep the idea of potentially outsourcing work in mind, maybe even ask around if the community would be willing to sponsor that or advance the payment.
But start with a group of people, sourced from the community, that are willing to commit to the task and the work in a structured and organized team effort. Do some research first to understand the task and the options we have; don’t focus on wasm before we can explain the why, and how it would be integrated. Make the selection of the vm tech a transparent decision process that documents the pros, cons and hows.
Then we can decide if we have enough resources in the community to realize it, or if we have to hire externals and how. But the groundwork should be laid and decided on by the community.
At least try it that way. If it turns out that we’re unable to finish even those first steps (I’m not sure if we have enough momentum tbh), then we can just take Kaine‘s advice for wasm and use the community only as a source of the required liquidity.
Are we at that point already? Serious question.
3 Likes