VegaWallet and Covault Partner to Bring Dash Payments to Cannabis DispensariesVegaWallet, the comprehensive cryptocurrency wallet and merchant solution that recently integrated Dash via BitGo, will now be partnering with CoVault crypto ATMs to provide additional fiat on-ramps, as well as launch a new PoS solution specifically geared towards cannabis companies. Read more here : https://dashnews.org/vegawallet-and-covault-partner-to-bring-dash-payments-to-cannabis-dispensaries/Credits : NibiruHybrid Source : https://bitcointalk.org/index.php?topic=421615.msg51172033#msg51172033VegaWallet partnering with Dash to utilize some of the first Evolution integrations
Both consumers and merchants are ideally looking to make their transactions as quickly as possible while also saving money and still getting what they want. Thus, it makes sense to use Dash to be able to quickly convert cash into Dash, in-store at the CoVault ATM, and then quickly turn around and spend that Dash at the VegaWallet PoS device, all while having each transaction being fully recognized as valid. Dash’s latest upgrade with automatic InstantSend makes this quick and inexpensive secure transaction possible. VegaWallet CEO, Tarek Hajri, explains the benefits of this feature.
“We are excited to work with Covault on increasing the presence of cryptocurrency remittance for businesses that need it the most. We feel the partnership will open new avenues for greater transaction liquidity. Payments with Dash and other supported assets are the future of business.”
|
|
|
It seems to me that Dash has not yet fully opened. Because I'm sure that it can be much more than it shows now.
Give Dash some time and i'm sure it will shock the cryptoscene to its core. Dash so far has been a crypto project that essentially has been : * Misunderstood * Underestimated * Ignored The road has been long and tough for Dash but we are getting closer and closer to achieving the goals that were set for Dash so many years ago, to become mainstream adoptable, easy to use by both consumers and merchants and to become a network that is fully on-chain scalable.
|
|
|
LLMQ-Based ChainLocksA few cryptocurrency projects have made headlines recently due to threats of 51% mining attacks. In a 51% attack, a mining entity that controls a majority of hash power can secretly mine a separate chain that is longer than the public one, then publish it — causing a reorganization and orphaning previous blocks on the original chain. This can result in users of the network losing money as transactions in the invalidated blocks are also invalidated.
ChainLocks will significantly reduce the risk of a 51% attack occurring on the Dash network. A Long Living Masternode Quorum is selected, and each member signs the first block it sees — extending the active chain at the current height. When enough members see that block, they will propagate a message to all nodes in the network. When this message is received by a node, it rejects all blocks at that height that do not match the block specified by this message. This not only makes reaching consensus quick and unambiguous, it makes chain reorganizations below this block impossible.
This means that transactions can be considered fully confirmed after the first on-chain confirmation inside a block protected by ChainLocks, and there is no need to wait for more confirmations until a received transaction is considered secure. This feature also removes all incentives for miners to cause chain reorganizations by mining in secret, because a failure to publish blocks immediately could give an honest miner the opportunity to publish a block that would be locked by a LLMQ, and thus made irreversible. This would result in the secret chain being ignored when the malicious miner attempted to publish it. Link : https://blog.dash.org/product-brief-dash-core-release-v0-14-0-now-on-testnet-8f5f4ad45c96But what about the longest-chain rule?The longest-chain rule is one of the most important parts of Proof of Work based consensus. The idea is that every node should consider the chain with the most accumulated work as the locally active chain (but only if it is also valid by all other consensus rules). The reason for this rule is that otherwise it wouldn’t be possible to find consensus on which chain to extend. Nodes need to find consensus based on limited information, and the only reliable information which is viable for this is the information found from the chain of headers. Using only the accumulated work (calculable from the headers) makes sure that every node can disconnect and reconnect, and still find consensus at any time.
With ChainLocks, this rule is still in effect, but it can be overridden by a valid CLSIG message. Effectively, only the members of the responsible LLMQ are fully following the longest-chain rule, as they are the ones creating the CLSIG message in collaboration. As the CLSIG message can only be created if enough LLMQ members agree, the presence of the CLSIG message serves as a proof that the referenced block was (or still is) the block resulting in the longest-chain.
This puts quite some trust into CLSIG messages and the Masternode network, but we consider this to be an acceptable tradeoff. The assumption is that the majority of the masternode network is honest, which is basically the same assumption applied to miners in a plain Proof of Work system.
The difference with ChainLocks is that miners AND Masternodes representing 51% of each of the layers would have to collude in order to perform a working attack. And even if an attack succeeded, the attackers would still not be able to cause deep reorganizations, as previous CLSIG messages can’t be invalidated by the attackers. The worst thing that could be achieved is to NOT sign blocks, which would be noticed by all nodes. Also, if any LLMQ with mostly honest masternodes signed a block in-between the attack, all previously unsigned blocks would become fully confirmed as well, making reorganizations for these impossible as well. Link : https://blog.dash.org/mitigating-51-attacks-with-llmq-based-chainlocks-7266aa648ec9
|
|
|
Great news! anti 51% attack ChainLock is now live on the mainnet! It will take some time before ChainLocks gets activated as we need support from miners first (80% to lock-in DIP8), but the highly anticipated update v0.14.0 has been rolled out today and thats good news.
|
|
|
Dash Core v0.14 on MainnetBinaries released and ready for deployment on mainnet Read more here : https://blog.dash.org/dash-core-v0-14-on-mainnet-ef2d0e49e29aDash Core Group is pleased to share that Dash Core v0.14.0 binaries are released and ready for deployment on mainnet by node operators.
This software release focuses on improving the user experience while increasing network security. Highlights of this release include:
Long-Living Masternode Quorums (“LLMQs”), which will increase scalability through improved consensus and expand the universe of potential use cases of the network. LLMQ-Based ChainLocks, which leverage LLMQs to improve network security by mitigating 51% mining attacks. LLMQ-Based InstantSend, using LLMQs to not only improve network scalability, but in combination with ChainLocks will allow for secure, real-time payments.
This release represents a major step towards making Dash the most user-friendly blockchain based payment system in the world. Long wait times make it hard for today’s crypto networks to truly compete with traditional payment methods like credit and debit cards. For a user trying to purchase groceries, for example, waiting more than a minute for a transaction to process simply isn’t acceptable. Beyond this, once a payment is received, users accustomed to traditional payment methods expect to be able to re-spend that received money immediately.
Other networks that have managed to reduce wait times have typically done so at the cost of network security by overly centralizing the authority over which transactions go through and which don’t, creating greater opportunity for manipulation and attack. Dash, on the other hand, will provide users with the real-time payments they expect at an extremely high level of security through the second layer masternode network. Someone who wanted to try to manipulate or attack the system would need to spend hundreds of millions in USD to do so. Credits : tungi17 Source : https://bitcointalk.org/index.php?topic=421615.msg51165071#msg51165071Time for some updating -qwiz
|
|
|
Dash Platform, DAPI, and Drive Value Propositions Further Enhances Dash NetworkDash Core Group (DCG) has released more information on the value proposition of the Dash Platform, which consists of Dash DAPI and Dash Drive. The Dash Core Group has plans to upgrade the network through protocol upgrades including creating “the development of the most user-friendly crypto wallet to date”, but to do so requires building out backend services. Read more here : https://dashnews.org/dash-platform-dapi-and-drive-value-propositions-further-enhances-dash-network/Credits : NibiruHybrid Source : https://bitcointalk.org/index.php?topic=421615.msg51152772#msg51152772In order to facilitate the development of this new wallet, as well as many other use cases, DCG is building Dash Platform, an application development platform leveraging Dash’s masternode network and blockchain. Comprised of two main architectural components, Drive and DAPI, these components turn the Dash p2p network into a cloud, through which developers will be able to integrate their applications. For our MVP release, the platform will primarily act as a Database as a Service, using data contracts to define custom data structures for applications, storing that application data on our masternode network, and notarizing that data via our blockchain.
Dana Alibrandi, Product Owner at Dash Core Group, further outlined that both Drive and DAPI will be written in written in Node.js and that “Dash Platform will be available for development as part of Release 1.0”. However, they “will continue evolving the platform, eventually providing developers with a full stack for development” after the initial release. Till now DashDrive and DAPI were always a bit vague and conceptional to me, but with the move to build Dash Platform (which aims to implement these two elements through Node.js) things are starting to take form. -qwiz
|
|
|
I skimmed the thread, so I apologize if my questions were asked or answered.
I love how Dash is aggressive in S. America. So much of crypto is pure speculation (buy and hope it goes up, then sell to somehow else). So see easy applications and actual retailers embracing it, is kind of the dream for crypto (or should be)
With Dash, does the blockchain/confirmations work the same? Is there a risk for doublespend like bitcoin? If paying at a retail outlet, are you made to wait until the transaction has a confirmation? (I saw the video of the girl paying for chicken and it seemed fast, but I've done Dash transactions where it seemed like sometimes it can be a few minutes between confirmations)
With Dash previous update v0.13 it became possible for Dash to enable InstantSend on small transactions (4 input amounts or less) automatically with no additional costs. This will get you : Instant payment with confirmation within a few seconds Available and spendable by receiver right away Locked against double spending Note : This is currently about 90% of the transactions on the Dash network. Dash also has the optionally InstantSend to be used on any transaction for a small fee, regardless of the size of transactions. Available right away and spendable by receiver after 1 proof of work confirmation, if i understand it correctly Locked against double spending Then you have the Dash transactions that contain more then 4 inputs and are not send through InstantSend, those transactions will get confirmed through proof of work and are normally considered secure after 6 confirmations. They dont have a specific locking mechanisme and are in principle the same as how Bitcoin does its confirmations, but then 4 times faster then Bitcoin. With Dash next update v.0.14 there will be LLMQ-based (Long Living Masternode Quorums) InstantSend. Keep an eye out on its release as that should provide you wilth more specifics. Link to definition of InstantSend : https://docs.dash.org/en/stable/introduction/features.html#instantsendLink to definition of Automatic InstantSend on transactions of 4 inputs or less : https://docs.dash.org/en/stable/developers/index.html#understanding-sporks(see spork 16) Link to blog about LLMQ-based InstantSend : https://blog.dash.org/product-brief-dash-core-release-v0-14-0-now-on-testnet-8f5f4ad45c96Note : Any transaction that gets locked through ChainLocks will be totally secure and locked against doublespending after just 1 transaction confirmation (instead of the normal 6 transaction confirmations).
|
|
|
https://coinmarketcap.com/I sense a shake-up in ranks developing between these cryptocurrencies... Edit : well, that didnt take long... I guess we will see some back and forth in ranks before the dust settles and a clear picture emerges. Needless to say i kinda like current picture already But with v0.14 around the corner and Dash Evolution scheduled for later this year, i'm exspecting an even better picture
|
|
|
Analysis of active addresses: Bitcoin, XRP, Dash, and Dogecoin see major growthRead more here : https://cryptoslate.com/analysis-of-active-addresses-bitcoin-xrp-dash-and-dogecoin-see-major-growth/The cryptocurrency with the most activity on its network was Dash, which saw a massive spike in usage in Venezuela, where sanctions and inflation pushed people into using the fast and reliable Dash. The network saw a 58 percent increase in the number of active addresses and went from 46,000 to over 74,000 in a single year.
|
|
|
If i could get a dash for everytime Icey used the word REKT with Dash, i would have a lot more masternodes But lets be serious here, old troll(s) trolling Dash again in this ANN thread is a good sign, it shows that they still care about Dash .. care deeply. And i love that they care about Dash this much, that they feel pressured to post here again (and again). Forward and onward with the caring, dear troll(s). A troll that cares works much harder at trolling, then a troll that does not care. - qwizzie
|
|
|
This Week (May 16th) at DCG :- DashCore updates for the final v0.14 release candidate - Updated platform components to accept historical filtered blocks from Core in order to support SPV functionality - Coded outbound contact activity and addressed some UI issues on DashPay - Coded payments to blockchain user contacts on DashWallet iOS - Optimize DashJ DMN Performance and added special transactions to the bloom filter on DashWallet Android read more here : https://blog.dash.org/product-update-may-16-2019-6acae277bd9aCredits : tungfa Source : https://bitcointalk.org/index.php?topic=421615.msg51087382#msg51087382Looks like Dash partners are given the time to test v0.14.0 a bit, which means my earlier initial prediction of a launch date of 15th of may 2019 for v0.14.0 (based on code of DIP0008 starting at 15th of may) was in fact wrong. Also there was a bug found recentely that needed fixing.
Only a few v0.14.0 pull requests are now still remaining (https://github.com/dashpay/dash/pulls), so it looks like this will be the final release candidate (as also mentioned above). After v0.14.0 is released on mainnet, testing will most likely concentrate on v0.14.1 (which will be a smaller update / minor update). -qwiz
|
|
|
|