Amended application for the bit.country m2.#696
Conversation
initial draft for m2.
Finalised the tasks in the milestone.
minor milestone text update
update team member
update image.
Change the amount to be USD as required.
Add bootstrap tasks for launching testnet.
Restructure and update wording to improve clarity of deliverables. Add summary and considerations sections.
Tech stack and changing NFT native to support NFT
update Duration
|
|
Noc2
left a comment
There was a problem hiding this comment.
Thanks for the PR. Could you update the original contract and not create a new file?
|
Thanks @Noc2 for the feedback, I just updated the original contract here |
semuelle
left a comment
There was a problem hiding this comment.
- Regarding
1b, instead of leasing functionality you want to implement fixed price sales? And this will be implemented within the Continuum pallet? - Can you expand on how
NFT Sign Supportworks? Do you store any information on-chain? - What does
NFT-Future-Event (e.g. time capsule)mean? - As a seller, what motive would I have to limit my sales to a local NFT market?
|
Thanks @semuelle. Please find the answers below.
Yes, due to a big impact on coordinates change on the map engine after the lease expired as well as the business logic, we would like to park the leasing for now. We instead offer the fixed price set by the council for a certain period so metaverse can buy Continuum spot at a fixed price. The logic is on Continuum pallet.
Sign to support NFT feature allows NFT holder can gain trust by getting signed by supporters, they can optionally contribute token which holds in that specific NFT fund. This not only support NFT financially but also publicity by number of supporters. We store all information of supporters e.g AccountId on-chain.
It's a special type of NFT that is only run by a game engine in a specific block. The execution logic handled off-chain.
There are some items in bit.country only available in local NFT market e.g land, subdivisions of that local metaverse. Global marketplace is designed for network-level item e.g raw land, global building, avatars and games. As a seller, really depends on what type of product you are selling. Hope it answers your questions. |
alxs
left a comment
There was a problem hiding this comment.
LGTM. When do you intend to deliver?
Noc2
left a comment
There was a problem hiding this comment.
Looks good, but I have one more request: Could you maybe add the programming language to the deliverables? This might help to clarify a few things, for example I’m currently not sure how NFT Market will be implemented (UI, CLI, etc.).
Thanks @alxs. We are adding some more validation and unit tests on the newly added features to ensure all conditions are covered. We tend to make a delivery PR by the end of the week. |
Thanks David @Noc2. I just updated the programming languages, the deliverables are developed on-chain so mainly Rust. The NFT marketplace deliverable logic is handled purely on-chain, we also will share the fully functional version through either Docker or UAT access. |
So, just to double check: A front-end is not part of this deliverable only pallets, correct? (because you now added the programming language of the UI as well). |
Yes, that's right. A front-end is not part of this deliverable. We can demonstrate the UI on Docker or give the team access to the UAT environment. |
semuelle
left a comment
There was a problem hiding this comment.
Thanks for the clarification. Works for me.
Good day,
As suggested in the original m2 application, we have amended the scope and deliverables in this application.
Changes logs.