Jump to content

tungfa

FORUM MOD
  • Content Count

    1,059
  • Joined

  • Last visited

  • Time Online

    12h 13m 24s

Community Reputation

205 Trusted Reputation

6 Followers

About tungfa

  • Rank
    Dash Moderator

Personal Information

  • Gender
    Not Telling
  • Country
    United States

Recent Profile Visitors

11,862 profile views
  1. Sentinel v1.3.0 release | Dash Forum Sentinel v1.3.0 is now released! Please update your MNs per the usual method (cd /path/to/sentinel && git pull). edit: To clarify, all mainnet and... Sentinel v1.3.0 is now released! Please update your MNs per the usual method (cd /path/to/sentinel && git pull). edit: To clarify, all mainnet and testnet should be updated to this version. edit2: Link to Sentinel on GitHub: https://github.com/dashpay/sentinel This release includes optimizations to how governance objects are represented in memory and handled in Sentinel, and (along with changes released in DashCore v12.3) allows for a newer, simpler JSON format governance objects. If you are a normal user / MNO, you only need to update Sentinel to the `master` branch, version 1.3.0. No further no action is required. If you are a developer of special tools like DashCentral or DashNexus, some other action could be required, so please read on. Specifically, the multi-dimensional array and un-necessary string field are removed, leaving only the core JSON Object to be parsed and processed. This can affect how 3rd party tools parse governance objects. If you have a tool which parses governance object JSON, you should be prepared to parse either the old legacy or new formats. To demonstrate, take the example for a proposal to buy Jack Sparrow a new ship (ahem, Captain Jack Sparrow, sorry...): Legacy format: Code: [ [ "proposal", { "end_epoch": 1547183994, "name": "jack-sparrow-new-ship", "payment_address": "yYe8KwyaUu5YswSYmB3q3ryx8XTUu9y7Ui", "payment_amount": 49, "start_epoch": 1521429194, "type": 1, "url": "https://www.dashcentral.org/black-pearl" } ] ] New simplified format: Code: { "end_epoch": 1547183994, "name": "jack-sparrow-new-ship", "payment_address": "yYe8KwyaUu5YswSYmB3q3ryx8XTUu9y7Ui", "payment_amount": 49, "start_epoch": 1521429194, "type": 1, "url": "https://www.dashcentral.org/black-pearl" } You'll notice that the gobject type string (1st of inner array) is removed and gobject type is identified by the "type" field. Type 1 = proposal, type 2 = trigger. No other types should exist. Sentinel will begin creating superblock trigger objects (candidate superblocks) in this new format. DashCore was updated in v12.3 to support either format, but any tools used to parse this (e.g. possibly DashCentral or DashNexus or other integrations) will need to be updated to support either. I am happy to assist if any one needs help, please contact me with any questions. Nathan Marley Dash Core Team
  2. The 'Wal-Mart' of Venezuela Has Started Accepting Bitcoin - Bitcoinist.com As Venezuela is in the grip of hyperinflation, a large local Wal-Mart-like department store has started to accept bitcoin for goods. Cryptocurrencies: A As Venezuela is in the grip of hyperinflation, Traki, a large local Wal-Mart-like department store, has started to accept bitcoin for goods.
  3. https://twitter.com/altthirtysix/status/1062788138198687746
  4. From 6th to 8th of November 2018 Jan Heinrich Meyer (Dash Embassy D-A-CH) Alexander Block ( @codablock) and Jon Durdel joined the GENOhackathon to bring cryptocurrencies to the masses by integrating them in the existing infrastructure of the GENObanks. This is the initial 1-minute-pitch: https://www.youtube.com/watch?v=jjki6hR0fYY The "answer" from DZ direct : (please share) https://twitter.com/dzbank/status/1062335776984391680?s=21
  5. Dash Sees "Mixed Signals on User Growth", Active Adresses Jump by 36% Dash, an open source cryptocurrency, is seeing more and more adoption, especially compared to the results a year ago, but the total payment volume and number of downloaded mobile wallets has been decreasing, according to their Q3 results.
  6. https://blog.dash.org/product-brief-dash-core-release-v0-13-0-5d7fddffb7ef If you have not yet read our announcement on the release name changes, please check it out here. Dash is a global payments network with its own cryptocurrency offering businesses and individuals instant payments for less than a cent per transaction. Our goal is to provide users with a better way to pay and get paid. We are in the process of rolling out a series of upgrades to our system dubbed “Evolution” to make Dash the most user-friendly blockchain-based payment network in the world. Available to anyone who wants to use it, the system runs on a distributed governance system operated by a network of masternodes. Masternodes enable Dash’s fast, secure payments by reaching consensus via “quorums” on the validity of transactions. Our development team recently introduced several network upgrades to Testnet which, after sufficient testing, we plan to introduce to Mainnet in Release 0.13.0. This release focuses on improving consensus methods on the network. It includes: Automatic InstantSend, which will improve the speed of most transactions at no additional cost; A deterministic masternode list to provide a single source of truth for clients validating transactions; Special transactions to accommodate non-financial transactions on the blockchain; A third masternode key to enable delegation of masternode voting; and Several improvements to private transactions. What are the highlights? 💨 Automatic InstantSend for Simple Transactions — No Extra Cost InstantSend payments allow users to exchange payment instantly using Dash’s masternodes. When a user sends a payment via InstantSend, a quorumof 10 masternodes is selected for each input of the transaction. The transaction is then “locked” when a majority of masternodes for each input agree that the input they are responsible for is valid, thus preventing double-spending. With Release 0.13.0, the system will automatically attempt to lock any transaction with 4 or fewer inputs — which are referred to as “simple” transactions — and remove the additional fee for InstantSend, so only the standard transaction fee applies. These transactions make up over 90% of all transactions on the Dash network — which means the majority of Dash transactions are about to get even faster, at no additional cost. 📝 Deterministic Masternode List When a quorum is used (for example, in an InstantSend transaction), nodes sometimes calculate different quorum sets to validate a transaction. Each node maintains its own individual masternode list through peer-to-peer messages, instead of pulling data straight from the blockchain. These discrepancies can result in problems with consensus and limit the possible uses of quorums. The deterministic masternode list is derived from information found on the blockchain itself, providing a single source of truth for all clients wanting to verify transactions. This includes SPV wallets, which historically have relied on trusted SPV servers to relay transactions. 🗝🗝🗝 3 Masternode Keys: Owner, Operator and Voting Today, a masternode owner has two keys for their masternode: (1) key to show they own the masternode, and (2) key to operate the masternode and also use it to vote. However, operating a masternode requires the operator to be online at all times in order to maximize rewards. The current system allows masternode owners to delegate the 2nd key to a third party, but then the owner must either give up the ability to vote, or maintain frequent contact with the third party to discuss votes. With the 0.13.0 release, we will break the 2nd masternode key into two, so masternode owners can have the flexibility to either retain or delegate voting as they wish. 💥 Special Transactions Traditional transactions only have inputs and outputs, which makes them useful for financial transactions — but not for transactions that carry additional data. There are workarounds, but they require developers to manipulate the current system in inconsistent ways to enable non-financial transactions. Special transactions provide new structures to enable non-financial transactions on the blockchain, thus laying the groundwork for many future uses of the Dash payment system. 🛡PrivateSend Improvements Dash users have the option of using the PrivateSend feature to protect their financial privacy. This way, no one can see the origin of the funds that were used, the same way you can’t deduce the origin of the paper cash in your wallet. It works by breaking transactions down into a few standard denominations of Dash (.01 Dash, .1 Dash, 1 Dash, and 10 Dash) and then “mixing” these with other transactions, all without the funds ever leaving a user’s wallet. Updates to PrivateSend in 0.13.0 will speed up the mixing process slightly, as well as introduce an additional denomination of .001 Dash. Anything else? Yes! All network operators will need to update to 0.13.0 as soon as possible once the release goes out. Please check out this post for detailed upgrade and testing instructions. What’s next? The next release will include, among other things, Long-Living Masternode Quorums. Stay tuned for more information on this and the other exciting features of that release.
  7. Dash Core Group Q3 2018 Summary Call - 12 November 2018
  8. https://twitter.com/staydashy/status/1061777034232373249?s=21
  9. v13.0 Testing | Dash Forum Release candidate v0.13.0.0-rc1 is ready for testnet! :) Github release candidate: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc1 Release... Release candidate v0.13.0.0-rc1 is ready for testnet! Github release candidate: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc1 Release notes are not ready yet and will be prepared in the next few days. Post will be updated. Gitian sigs can be found here: https://github.com/dashpay/gitian.sigs Before testing: Make sure you made a backup of you mainnet datadir somewhere or at least a backup of wallet.dat/dash.conf/masternode.conf; Or use the -datadir and -conf parameters to use completely different directories. As this release deploys DIP2/3/4, we'll have to ensure all existing and new functionality works as expected in multiple stages of the deployment. The stages of the deployment are as follows: 1. Full nodes, Masternodes and Miners upgrade their nodes to the latest release 2. Miners will start voting on the BIP9 deployment for DIP3, but only if they see enough MNs upgraded (this is automated) 3. After enough blocks with the proper BIP9 bits have been mined, DIP3 will activate but stay in "compatibility mode" 4. In this "compatibility mode", the existing non-deterministic masternodes should continue to work as expected 5. Now MNs can start registering their MNs as deterministic masternodes. Detailed instructions on how to do this will follow when the time arises. 6. Even the registered MNs will continue operating in the "compatibility mode" and will appear in "masternode list" as expected. InstantSend, PrivateSend, Governance, MN payment logic and so on should continue working as usual. 7. We will watch the progress of MNs upgrading to DIP3. When we see enough of these, we'll turn on spork15 (SPORK_15_DETERMINISTIC_MNS_ENABLED) 8. This is the point were all of us will be silent for a minute...as we say goodbye to all the non-deterministic masternodes. We'll see the output of "masternode list" immediately switch to the deterministic list (dropping all others). We'll also see the network go kind of silent, as all the bloat of masternode list synchronization disappears from the network...no more MNB, MNP, MNW, ... messages. We are at stage 1. and I will update this line every time we move forward to the next stage. We will have to perform full testing of all functionality in stages 1., 3. - 5. and 8. (so, 3 times in total). This includes: What/how to test: - Check if normal transactions are still working, perform some automated load testing if you want - Check if creating and voting on proposals work. Also check if winning proposals get paid and other don't. - There were improvements in PrivateSend, please test if mixing still works for you. It is very likely that mixing will not be working as expected in deployment stage 1. and 2. - Check if InstantSend is still working (it might fail in the beginning as not enough MNs are available/upgraded atm) - Starting with stage 3., test if automatic InstantSend locks for simple transactions are working as expected. - Run a masternode or two, make sure it is paid. We're happy for everyone that also participates in the whole upgrade process from normal/old MNs to the deterministic MNs. Instructions on how to upgrade will follow when we reach stage 5. What else you can do: - Report serious issues (crashes/hangs/GUI glitches) : https://github.com/dashpay/dash/issues/new Testnet tools (explorers, faucets, pools): https://www.dash.org/forum/threads/testnet-tools-resources.1768/ MNOs: Wiki: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/118162190/Masternodes+under+testnet Sentinel : https://github.com/dashpay/sentinel/tree/develop DMT support for deterministic masternodes is currently still work-in-progress. Maybe @Bertrand256 can add some info/instructions when he is ready. Until then, users will have to manually sign the DIP3 messages with the collateral key on HW wallets. As said, detailed instructions will follow when we reach stage 5. NOTE: Make sure you pulled Sentinel from `develop` branch and changed network to `testnet` in `sentinel.conf`. If you already have a mainnet masternode on the same server, do NOT run testnet masternode in the same datadir as your mainnet masternode (i.e. `.dashcore`). Create new folder specifically for testing (e.g. `.dashcore_test`) and make sure you use `-datadir=<yourtestnetdatadirhere>` cmd-line parameter for dashd and dash-cli. You'll also need a separate crontab line for testnet Sentinel. If you are not 100% sure what you are doing, I'd recommend setting up a new machine/instance for testing purposes only instead of reusing your mainnet server.

Cryptocurrenytalk Logo

 

News, information, and discussions about cryptocurrencies, blockchains, technology, and events. Blockchaintalk is your source for advice on what to mine, technical details, new launch announcements, and advice from trusted members of the community. Cryptocurrencytalk is your source for everything crypto. We love discussing the world of cryptocurrencies.

 

   
×

Important Information

By using CRYPTOCURRENCYTALK.COM, you agree to our Terms of Use.