Proposal “dashparty---a-dash-token-metalayer“ (Closed)Back
| Title: | Dashparty - A dash token metalayer |
| Owner: | dashparty |
| Monthly amount: | 422 DASH (12616 USD) |
| Completed payments: | no payments occurred yet (3 month remaining) |
| Payment start/end: | 2020-04-15 / 2020-07-13 (added on 2020-04-04) |
| Final voting deadline: | in passed |
| Votes: | 433 Yes / 278 No / 113 Abstain |
| External information: | app.dashnexus.org/proposals/dashparty---a-dash-token-metalayer/overview |
Proposal description
*** This proposal is an already working product, we would like to get funding to further development and make it a GREAT product***
Dashparty brings to Dash the ability to be used for token economies. Sending and receiving Collectibles, Company shares, NFTs and any other kind of digitally representable bearer asset becomes a reality with the usage of this metalayer.
Included in Dashparty is a Decentralized Exchange (or DEX for short) which allows exchanging tokens in a decentralized manner without the need for intermediaries.
Dashparty is based on the excellent Counterparty software, which has worked on the Bitcoin blockchain since 2014. Bringing this stable and rock-solid
software to Dash will give token users a fast network to work with and lower fee cost that have plagued other blockchains in the past.
Dash holders will also see a benefit in this project as some important operations need to burn a small amount of Dash, thus lowering the Dash
supply and making remaining Dash more scarce.
Work has already been started, some of the budgetary concepts are taking into account already done work. Supporting this project with a Dash budget
will mean that we won't have to create an intermediary token swap phase to fund the project (Like it was done in Counterparty) and allow all operations inside the metalayer to be carried on to whoever has Dash balance.
Part of the budget will be dedicated at bringing NFT artists into the ecosystem through competitions which will be awarded Dash amounts according to user votes and some manual curation.
Also, some paid Press Releases will be made in order to get some attention of the general community and bring awareness to the project and its usefulness.
A more detailed proposal, using the older template found on Dash's website, can be found here.
Dashparty brings to Dash the ability to be used for token economies. Sending and receiving Collectibles, Company shares, NFTs and any other kind of digitally representable bearer asset becomes a reality with the usage of this metalayer.
- Token explorer http://dashparty.xchain.io/
- Wallet https://github.com/dashparty/dashwallet-desktop/releases
- Code https://github.com/dashparty
- Telegram group https://t.me/Dashparty
Included in Dashparty is a Decentralized Exchange (or DEX for short) which allows exchanging tokens in a decentralized manner without the need for intermediaries.
Dashparty is based on the excellent Counterparty software, which has worked on the Bitcoin blockchain since 2014. Bringing this stable and rock-solid
software to Dash will give token users a fast network to work with and lower fee cost that have plagued other blockchains in the past.
Dash holders will also see a benefit in this project as some important operations need to burn a small amount of Dash, thus lowering the Dash
supply and making remaining Dash more scarce.
Work has already been started, some of the budgetary concepts are taking into account already done work. Supporting this project with a Dash budget
will mean that we won't have to create an intermediary token swap phase to fund the project (Like it was done in Counterparty) and allow all operations inside the metalayer to be carried on to whoever has Dash balance.
Part of the budget will be dedicated at bringing NFT artists into the ecosystem through competitions which will be awarded Dash amounts according to user votes and some manual curation.
Also, some paid Press Releases will be made in order to get some attention of the general community and bring awareness to the project and its usefulness.
A more detailed proposal, using the older template found on Dash's website, can be found here.
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
|
No comments so far?
Be the first to start the discussion! |
"quantumexplorer_DASH
Dash iOS Developer
3 points ·
3 hours ago
I for one am concerned about their proposed protocol changes that would allow unlimited business logic on the L1 chain. This goes against what we are trying to build on L2. And then there's the fact that they are asking for quite a lot."
Does the proposal owner have a reply to this comment?
* If it's a lot or not on the funding side, that's a rather subjective matter. I honestly think we are bringing a lot to the table (and unlike most other proposals, we have an already working product, no "promises of future work" but rather "we have been working and here we are to make it more awesome").
From Bitcoin Core release 0.9.0:
"This change is not an endorsement of storing data in the blockchain. The OP_RETURN change creates a provably-prunable output, to avoid data storage schemes – some of which were already deployed – that were storing arbitrary data such as images as forever-unspendable TX outputs, bloating bitcoin's UTXO database.
Storing arbitrary data in the blockchain is still a bad idea; it is less costly and far more efficient to store non-currency data elsewhere. "
For the last few years we have been trying to make it so people don't want to store anything in L1 and give a better L2 solution, now we're not completely there yet I know. But creating a new transaction with a dashparty payload to add this info to L1 will (hopefully) soon be antiquated. I would instead just use OP_RETURN for now.
In term of funding, the asking price is not something I am taking into account, me writing about it before was just a reason I thought the proposal might be getting no votes.
In other things, please don't call the mobile freewallet port wallet Dashwallet, as the name is already taken and will lead to confusion among users.
Regarding non-financial data on L1, extracted from DIP2 https://github.com/dashpay/dips/blob/master/dip-0002.md :
"This DIP adds a basis for new transaction types that will provide on-chain metadata to assist various consensus mechanisms. This will allow for a more native way to implement new features which don’t naturally fit into the current concept of transactions."
This means that (at least on the moment this DIP was approved and implemented) non-financial on-chain metadata is not only tolerated, but also actively endorsed on the Dash blockchain.
I understand the rationale behind being against OP_RETURN and other data embedding shcemes (i'm also of the idea that certain meta-transactions shouldn't be on a L1, like betting, game actions and other volatile/transient operations), but there's no way to prevent it from being "abused" (from the deniers' perspective) so a better approach is to regulate and control them via a properly specced protocol.
This off course doesn't means there's stuff that should go on L2: i.e. the DEX is interesting on L1, but user experience is awkward and most people don't understand why the slowness and clunky native asset interaction.
"This DIP adds a basis for new transaction types that will provide on-chain metadata to assist various consensus mechanisms. This will allow for a more native way to implement new features which don’t naturally fit into the current concept of transactions." I either wrote that sentence or another of the co-authors did. What we meant was Dash protocol consensus mechanisms. I agree that we maybe should update the wording. I came up with the idea for DIP 2 and it was always for internal and bounded consensus mechanism. Bounded meaning that fields used are not blobs, but validated in L1 consensus.
The goal with L2 is to make devs have 0 incentive to use L1 at all, and all incentives to use L2. Though it is a problem I agree with solutions that are already present for L1, and with L2 not really out or mature.
I was enthusiastic about this proposal before, but I admittedly am unfamiliar with the ins-and-outs of the protocol. My vote has changed to reflect this new information.
The idea is good and there's existing code/website.
Anyway voting yes x12-13 (having node issues).
It could also be that some are against adding more stuff into L1, which is happening regardless of funding.
Regarding "negative" side-effects, the only one i can think of is more usage of the L1, bringing fees upwards.
Spreading Dash, increasing the size of the Dash community, increasing the Dash community's ability to be of service to other community's through easy integration with their wallets, these are all things that we need to do and support often and repeatedly in order to succeed.
As long as this functionality plays well with Dashpay and Evolutions new features, and from comments on various channels Ive become sure it will, then I see no reason to do anything but throw our support behind this proposal.
Question for the proposal owner and/or any dash developers who might want to weigh in: I know this was already discussed to some extent in discord but it might help if you could explain a bit more here about what are the differences between Dashparty and the evolution Dash Platform. Thanks --
This has been touched (although not in depth) in the dashparty channel on the dapps dev discord, and we've agreed that we need to finish the complete port to make further decisiones down the line.
Also i am not sure if adding a metalayer to Dash at this point in time (while we are still in the process of building out the Dash Platform) is the right move.