Jump to content

Snider

Administrators
  • Content Count

    1261
  • Joined

  • Last visited

  • Days Won

    23

Blog Entries posted by Snider

  1. Snider
    xcash project updateDear community,
    Today, we are starting a three part series of what to expect from X-Cash technology wise.
    Today we will discuss what is upcoming with the DPoPS infrastructure and X-Cash Core for the end of the year and the start of next year.
    What is DPoPS?
    The DPoPS (standing for Delegated-Proof-of-Private Stake) is a brand new and unique Delegate-Proof-of-Stake consensus integrated into X-Cash, an open-source fork of Monero which has since the beginning of the project brought new innovation to the privacy coin space (notably FlexPrivacy, public & private transactions on the same blockchain, from the same wallet).
    Updates for the end of the year
    Our plans for DPOPS (and xcash-core) until the end of year is to make it more stable, resolve any known issues, and add any performance or compatibility updates. Few issues remaining at this time, but the DPoPS needs to be 100% bug free before we add protocols on top of it. This is mainly due to the fact that protocols like instant send payments not only interact on top of DPoPS, but use a stripped down base of the core code from DPOPS in their code base.
    The plan is to include all of these into a xcash-core 2.1.0 update and a xcash-dpops 1.1.0 update that will be released at the same time. To review the code already added to these branches, they are located at
    https://github.com/X-CASH-official/xcash-core/tree/2.1.0
    https://github.com/X-CASH-official/xcash-dpops/tree/1.1.0
    These updates will include (currently added but not limited to)
    xcash-core
    Various enhancements to the server and syncing blocks methods
    Latest boost and other libraries compatibility
    Latest Ubuntu Linux compatibility
    latest GCC compatibility
    Fix Docker file
    Various updates to remove cryptnote legacy warnings and various C++ deprecated warnings, or libraries warnings
    xcash-dpops
    Various enhancements to the server and syncing blocks methods
    Latest Ubuntu Linux compatibility
    latest GCC compatibility
    Merge farmage PR #61 https://github.com/X-CASH-official/xcash-dpops/pull/61 that adds a cache for db DBFT checking
    Merge snakeway PR #62 https://github.com/X-CASH-official/xcash-dpops/pull/62 that fixes some thread unsafe problems
    Updated all DPOPS tools to latest versions (mongo, mongo tools, mongoc driver, nodejs)
    Fix all unit test
    Testnet Release Date
    We have for months needed to setup a testnet for the future of XCash. Not only to have a testnet of the live blockchain, but to safely test new updates and protocols to the DPOPS base protocol. We will also eventually need a testnet once smart contracts are released and other higher level features that will involve the community of developers.
    We will use this large update and end of the year timing to setup a testnet and run this update on the testnet before we deploy it to the mainnet. Their has been a lot of community support for running a testnet and we really appreciate the community support in the alpha and beta stages, but we want to draw long support for the testnet, just like the block reward is keeping the mainnet support going.
    We really want people dedicated to keeping the testnet going. A lot of people have expressed interest in running testnet nodes as extra servers and to continue to run their mainnet servers, or some people have only wanted to participate in the testnet. Their are also voters who dont have enough to participate in the mainnet but would like to run a server.
    We also dont want to run 20 servers like we did in the alpha with only 10–15 “community servers”, as we have seen the more realistic conditions the better.
    We have come up with a solution that we think will work great for all of the above.
    We will run a “open testnet” where anyone can run a server. The requirement is to be in the top 50 to produce blocks just like the mainnet. We will use a forked xcash blockchain (height will be close to current height when we start) and the blockchain will be re forked from the mainnet after 50000 blocks have been produced on the testnet, or 6 months if issues arrive during the testnet. This is to stay current with the xcash values of the mainnet. Everyone will be able to use their mainnet xcash values on the forked testnet (xcash value prior to the snapshot) and will move up and down the ranks just like the mainnet.
    We don’t expect servers to have voters like the mainnet, but we expect small voters and or people who are not currently participating at all, to try to participate in the testnet, since the pressure to run a node is very little and your knowledge of the xcash ecosystem will grow.
    The incentive to participate in the mainnet will be three different types of rewards (with real mainnet xcash) will be awarded each month to the delegates address on the mainnet
    Basically the top delegate on each of the categories at the end of the month (last block of the month) will be awarded 1 million xcash!
    http://delegates.xcash.foundation/statistics
    We think that this will give incentive for smaller voters or people not participating in the DPoPS to run their own server on the testnet.
    No release date has been given for the testnet and their is still some work to be done on the 2.1.0 and 1.1.0 branches, but we will let you know in advance before the testnet snapshot for round 1.
    Next Protocol
    Zach had a lot of time during the beta testing phase of DPoPS to research and work on some of the next protocols.
    As we have seen with the instant send video (https://www.youtube.com/watch?v=eemT3A3kGeg), that protocol is about 80% done and is almost ready for alpha. We also have another protocol that has not been mentioned until now. We believe that a voting protocol would be very useful for the community. It allows the team to propose a question to the community, and for the community to let their DPoPS delegate know what they want. Then the DPoPS delegates vote and the results are not artificially inflated since we carried out the vote on the xcash blockchain using the delegates and DPoPS infrastructure.
    Those will be the next protocols as both have coding done. We have not made a decision yet on which one, but of course we would love to hear the communities feedback on which one they think is more important at this stage.
    Let us and Zach know on discord as this will be useful info.
    If you have already not seen the demo of the instant send payments on xcash, you can watch that on Zach’s YouTube channel (zachy zone)
    https://medium.com/media/4c0c9727885aea11403582c4dc05d77b/hrefWait what about a rebase?
    A rebase (updating the xcash-core base monero code from 13.0.4 to the latest) is always on the table with the modular design. Since most features will be built on top of DPOPS (which is created from scratch) it will be possible to rebase to another version of monero at any time. As of now this is not in the immediate plans, but as time goes on and protocols get built, it will make sense at some point to rebase. We have not seen any features yet that makes us want to rebase, but future talked about features like stringct (ability to set the ringct count to greater than 1000 not less than 100) will be a big reason to rebase
    Thank you everyone.
    Project Update: Core and DPOPS 2021 into 2022 was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
    View the full article
  2. Snider
    September 2021
    General
    The incredible commitment of the XCASH Community made it possible that the XCASH QuickSwap Liquidity Program almost reached the 1M TVL goal (even during this short market breakdown)! With $2.1+ million of dQUICK deposits, over 3.5b XCASH and 950 QUICK in the pool, X-CASH is now stable in the TOP 10 list of Dragon Syrup tokens! Now the 1M++ TVL goal is just a matter of time!
    Thank you all for your commitment, happy farming and keep adding liquidity!
    Please notice our new Requests For Contribution:
    IOS Wallet development
    https://github.com/X-CASH-official/builders-program/issues/13 Ledger Nano Wallet
    https://github.com/X-CASH-official/builders-program/issues/11 The DNS issue has been solved! Sorry for this inconvenience! After this extremely unpleasant incident we will finally say goodbye to OVH, as their support & reaction time is …. .
    Don’t miss the current X-Cash Exchange Quiz and win 3Million XCASH!
    Acquisition & project development
    The long-awaited Exchange listing is on its way! Guilhem has entered into negotiations and so far it looks very good. At present, Guilhem can tell the following:
    Expected announcement of the exchange name in the next 10 days Expected listing in less than a month. Please bear in mind that negotiations are ongoing and the details of the cooperation are still being worked out, and therefore these are still confidential.
    We are all very excited and ofc impatient and would love to fast-forward the time now!
    WXCASH & X-Bank
    During the last weeks, of constant thinking, analysing and experimenting, Denis did a great job on improving X-Bank and wXCash. All the issues regarding stuck WXCASH deposits are fixed now! He also introduced a few major improvements to the WXCASH deposit processor, by adding a cache of Polygon blockchain during the sync. The cache now contains “blocks tails” which are reused as many times as possibly while syncing users’ WXCASH wallets to make the process faster. This feature gave us a significant improvement in performance, resources usage, and a decrease in the number of Infura requests.
    Here are the achievements in a nutshell:
    Deposit sync became around 20x times faster: from around 2 minutes to 5–6 seconds. Be aware that sync happens every 100 blocks. In other words, it requires 100 confirmations on Polygon network for a transfer to appear in X-Bank. Number of Infura requests (actual calls X-Bank does to Polygon network) got cut 7x times; from ~200k requests per day to 25–30k requests per day. Denis will post a roadmap for the X-Bank project in the next few weeks, so don’t miss it and stay tuned!
    X-Payment
    Lovro put on his ninja dev costume and integrated a network manager so X-Payment does not crash any more and as the “official” Discord library has ceased with its development he migrated to a new one. Further more he developed and tested with caga”Crypto”palitos successfully the X-Payment Merchant. And, yes, it works!
    The X-Payment Merchant status is now:
    Backend script processing expired roles → Done Server owner merchant activation → Done Server owner command to monetize role → Done Discord member purchase command → Done Global X-Payment, server stats, members stats updater → Done Relay of merchant activity to explorer → Done Server Owner merchant earning withdrawal command → Done Merchant stats integration into server stats UI → Done Member check for monetized roles on server command → Done Member stats to UI → Done Member command to check current state of purchased/live roles → Done Server owner perk management commands → Done We are excited to see the release of the X-Payment Merchant by mid-end October 2021, and we already started preparing & building a X-Payment roll-out campaign.
    DPoPS
    DPoPS is running smooth and stable. Zach is intensively monitoring, as well as reviewing & testing the PR’s by snakewaypasser and farmage. It should not be much longer, and we will soon see a new DPoPS update.
    In the upcoming days, Zach will publish an article with a roadmap for DPoPs, so don’t miss it, stay tuned and happy staking!
    Community
    We hope you did not miss the previous AMA with Guilhem! Actually impossible if you have seen the cool teaser video made by Scheppy:
    https://medium.com/media/28e48fb6160f8b2f6968cfea135ee0ba/hrefIf you really missed it, read about it here:
    [AMA RECAP] X-CASH @ Blockchainspace
    Also take a look at the nice new infographic made in collaboration by our community members Juh and Ju:
    A very detailed up-to-date & step-by-step “Beginners guide to WXCASH(Polygon) and Quickswap“ is also being worked on. A few parts are already available at Ju’s medium blog, take a look: https://julien59247787.medium.com
    As you might have already seen, Worawut released some new nice x-cash art-pieces, like this one:
    Also, the X-Amba program gets an update (rebranding and restructuring), to make it scalable, reproducible, and attractive. We will effectively be merging the X-Army concept with the X-Ambassador concept to create a new type of structure. As a result, we’re introducing a new retribution structure, new roles including a democratized ascension process, and a new program name — XCadia. XCadia is looking for brand & support ambassadors, graphic designer, video editors, copywriters and any X-Cash enthusiast willing to contribute and do whatever is needed to make X-Cash a Top 10 cryptocurrency!
    And finally, special thanks to Zaffy’s & Francisco’s unbeatable Telegram support and Yurri’s non-stop Twitter action!
    Team report and community update was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
    View the full article
  3. Snider
    We are happy to announce that Monero P2Pool is live on the Monero network and binaries have been released.
    What is Monero P2Pool?
    Monero P2Pool is a peer-to-peer Monero mining pool developed from scratch by SChernykh (also known as sech1). P2Pool combines the advantages of pool and solo mining; you still fully control your Monero node and what it mines, but you get frequent payouts like on a regular pool. P2Pool as a concept was first developed for the Bitcoin blockchain but was never fully realized due to certain limitations, mainly because it had a problem with orphaned blocks which is solved in Monero P2Pool with uncle blocks.
    P2Pool has no central server that can be shutdown/blocked because it uses a separate blockchain to merge mine with Monero. There's no pool admin that can control what your hashrate is used for or decide who can mine on the pool and who can't; It's permissionless!
    All pool blocks pay out to miners immediately. Because there is no pool wallet, funds are never in custody; It's trustless.
    P2Pool uses PPLNS payout scheme, has 0% fee and 0 XMR payout fee (by design, fees can't be added). Everyone in the PPLNS window is rewarded directly via the coinbase transaction reward. Minimum payout is less than 0.0004 XMR due to the very efficient miner reward transaction format; each individual miner payout takes only 38 bytes on the Monero blockchain!
    Why Monero P2Pool?
    There's been some worry about mining pool centralization and the possibility of 51% attacks. Since atomic swaps went live (solving exchange delisting/KYC threat), mining is now the most centralized part of the Monero ecosystem. Currently, one pool accounts for almost 40% of Monero's network hashrate. This is not a stable situation long-term because a pool admin can be pressured to do malicious things, shutdown their pool, or expropriate funds without paying miners.
    How does it work?
    P2Pool is a sidechain to Monero, and P2Pool blocks are potentially Monero blocks. Each miner submits block templates that include a payout for all of the miners that currently have shares in the PPLNS window. High quality block templates are added to the P2Pool blockchain as blocks which count as "shares" for the miner who found them.
    If a block is good enough to be a Monero block it is also submitted to the Monero network to be included in its blockchain. Once the Monero block is confirmed by the network, those miners are directly paid in the coinbase transaction because they were included already in the block. If P2Pool "shares" are found at the same block height as an existing share, it is included as an uncle block (worth 20% less than a normal share) so you can still get paid for it (uncle blocks can be submitted up to 3 blocks behind the current height and still be included).
    Features
    Decentralized: no central server that can be shutdown/blocked. Permissionless: there is no one to decide who can mine on the pool and who can't. Trustless: there is no pool wallet; funds are never in custody. All pool blocks pay out to miners immediately. PPLNS payout scheme 0% fee and no payout fee Less than 0.0004 XMR minimum payout Fast block times, down to 1 second Uncle blocks are supported to avoid orphans - all your shares will be accounted for! Advanced mempool picking algorithm, it creates blocks with better reward than what monerod solo mining does Password protected private pools Configurable PPLNS window size and block time NOTE: Setting a password or changing any settings in config.json will create a separate sidechain. Only do this if you know what you're doing.
    Getting Started
    P2Pool Download P2Pool GitHub P2Pool Monitoring Page Note since P2Pool is decentralized, this is only a monitoring page. P2Pool Libera.Chat IRC and Matrix channels: #monero-pow and #p2pool-log Donations
    If you'd like to support further development of Monero P2Pool, SChernykh has a donation address on his GitHub page.
    View the full article
  4. Snider
    When constructing a new transaction, a Monero wallet references a past output a user received in a prior transaction, and uses it as an input to the new transaction. Today, the wallet mixes this output with a set of 10 decoy outputs selected from other people's transactions from across the blockchain (ring signature). Thus, an observer cannot tell which among the 11 total outputs is the real one a user spends in a transaction, obfuscating the link from the user's new transaction to their prior transaction. The decoy selection algorithm specifically handles the selection process for choosing which decoys to mix real outputs with when constructing a transaction.
    Between Monero versions v0.14.1.0 and v0.17.2.2, the core wallet code had two bugs in the decoy selection algorithm that impacted Monero users' privacy:
    The algorithm sometimes ignored very recent spendable outputs for consideration as decoys, thus rendering it clearer when users spent outputs immediately after the outputs were able to be spent.
    If transaction volume were to increase substantially over a sustained period of time, then wallets would eventually construct transactions that reveal real outputs in the vast majority of cases.
    Both have been patched in v0.17.2.3 and it is highly recommended to upgrade as soon as able.
    Users should also be aware that the implications of the first bug are not as severe as previously reported. It was widely publicized that as a result of the first bug, some very newly spent outputs observed on chain were guaranteed identifiable as real outputs spent in a transaction, however, this is not actually the case. Since publication, we learned that at least one popular light wallet (MyMonero) has been using a separate implementation of the decoy selection algorithm that did not have the bug. Therefore, MyMonero users could have feasibly constructed transactions that selected newly spendable outputs as decoys, which means newly spent outputs observed on chain were not guaranteed identifiable as real outputs.
    Note that having distinct implementations of the decoy selection algorithm is not ideal. Ideally, all wallets would conform to the same spec of the decoy selection algorithm to ensure transaction uniformity, so that transactions on-chain cannot be tied to a particular wallet implementation.
    Technical Explanations
    Applying the algorithm incorrectly (Bug 1)
    The decoy selection algorithm is designed to select outputs from across the blockchain based on observed spending patterns, as recommended in Möser et al. The paper's analysis uses spending patterns from earlier versions of Monero — where in some cases, the real outputs used in transactions could be deduced with certainty — in order to arrive at a distribution of Monero user spending patterns. The paper highlights that users were more likely to spend outputs received relatively quickly than they were to spend outputs held for a long time. The paper then recommends factoring in the observed spending patterns when selecting outputs from across the blockchain to use as decoys, rather than apply an equal probability to the entire set of outputs from across the blockchain. This way, newer outputs would be more likely to be selected as decoys than older outputs, thus better obfuscating which output is real in users' transactions.
    When the paper's recommendation was first implemented in Monero v0.13.0.0, the wallet correctly applied the observed spending pattern from the tip of the blockchain when selecting decoys. However, when the algorithm was upgraded in v0.14.1.0, the algorithm applied the observed spending pattern from 10 blocks prior to the chain tip. This was done because outputs younger than 10 blocks old are locked and cannot be spent, therefore it seemed logical to apply the distribution starting 10 blocks prior to the chain tip so as to only consider spendable outputs. However, the implementation ended up ignoring some very recent spendable outputs for consideration as decoys. Additionally, it caused the algorithm to select marginally fewer decoy outputs roughly 10 to 20 blocks old.
    This bug was patched in PR #7821.
    Divide by 0 (Bug 2)
    The upgrade to the decoy selection algorithm in v0.14.1.0 factored in block size variance in order to better match spending patterns and reduce bias toward selecting coinbase outputs as decoys. When selecting a decoy, the algorithm first determines the age in seconds that the decoy output should be (by using the distribution of known spending patterns, as discussed above). Then, the algorithm divides the expected output age in seconds by the average seconds spaced between each output observed over the trailing year, in order to arrive at the output in the chain that should be used as a decoy. If the number of outputs in a year is equivalent to the number of seconds in a year, then the average seconds spaced between each output over the year is 1.
    The calculation of average seconds per output had a bug where it would truncate the result. If the average seconds per output were to fall below 1, the result would have truncated to 0. When the algorithm divides the expected output age in seconds by 0, it ends up selecting decoys exclusively from the most recent spendable block on most systems. Thus, if output volume were to increase substantially over a sustained period, such that the seconds spaced between each output over the trailing year were to fall below 1 (i.e. the number of outputs over the trailing year exceeds the number of seconds in a year), then the algorithm would have selected decoys from the most recent spendable block in the vast majority of cases. At the time of this publication, the average seconds per output is around 1.7.
    This divide by 0 bug was patched in PR #7845.
    Conclusion
    Work to improve the decoy selection algorithm is ongoing. It has room for improvement to provide stronger protection to users under a wider set of circumstances. A call to arms: anyone with a background in statistics and probability theory is encouraged to join in discussions geared toward improving the algorithm. Discussions are frequent in the #monero-research-lab and #monero-dev IRC/Matrix channels. While innovative research to improve Monero's cryptography continues in parallel in order to substantially increase the number of decoys mixed with real outputs in a transaction (i.e. increase the ring size), research to improve the decoy selection algorithm's statistical obfuscation techniques is also receiving more attention. If you feel you have the requisite skills, keep in mind there is growing interest from the Monero community to actively recruit you to the Monero project. If you are interested, consider contacting a Monero workgroup.
    View the full article
  5. Snider
    Dear community,
    We are very excited to share the launch of XCASH on the Polygon Network with a liquidity mining program in partnership with Quickswap. The current APY is 1406.28% [Last update 09/09/21 12:26 UTC+0].
    In this article, we present what is the X-Cash project, its purpose, and what we have built in the past 3 years. If you are looking to farm XCASH you can directly switch to the tutorial section below.
    What is X-Cash
    X-Cash is a hybrid public-private coin with several features developed and added since 2018. X-Cash also includes an innovative consensus algorithm called Delegated-Proof-of-Private-Stake (DPOPS) that allows anyone in the network to obfuscate their stake and use it to vote for delegates in charge of the consensus. The current delegate ranking is available here.
    More information can be found here:
    X-Cash Website: https://xcash.foundation
    X-Cash Documentation: https://docs.xcash.foundation/applications/wxcash
    How to participate in the Polygon launch and farm token
    Program Details
    Liquidity Mining
    Provide liquidity $XCASH/$QUICK and earn $QUICK in return.
    Reward: $500k worth of $QUICK
    Start Time: September 8th, 2021
    Network: Polygon
    Reward duration: 90 days
    XCASH/QUICK pair: 0x30167fea9499c11795bfd104667240bdac939d3a
    Staking
    Stake $dQUICK in the X-Cash Dragon’s Syrup pool to earn $XCASH.
    Reward: $500k worth of $XCASH
    Start Time: September 10th, 2021 or September 13th, 2021
    Network: Polygon
    Reward duration: 90 days
    Contract address: (coming on September 8th)
    Tutorial — Step1: Get XCASH and QUICK
    You can buy XCASH directly on Quickswap Exchange (Polygon Network) on the XCASH/QUICK pair.
    You can swap XCASH to QUICK and vice-versaYou can buy QUICK directly on Quickswap with any asset or on most centralized exchanges like Binance.
    Tutorial — Step2: Add Liquidity to XCASH/QUICK to get LP Token
    Add your liquidity to the XCASH/QUICK pool.
    “Add liquidity” panel with XCASH and QUICK selected.A few hours after launch, the liquidity has already significantly increased and you can track its evolution here.
    A few hours after launch, the liquidity is already $380k with close to 25% of the Polygon circulating supply staked
    Tutorial — Step3: Stake LP token to get QUICK
    Go to the XCASH/QUICK LP Farming pool and stake your token to get QUICK.
    Tutorial — Step4 (optional): Stake QUICK to get dQUICK
    Additionally, you can stake the QUICK farmed to receive dQUICK in the Dragon’s Lair here. This is the pool where the transaction fees are collected and given back to QUICK holders. When you stake QUICK in the dragon’s lair, the amount of QUICK you receive from staking will always be higher than the initial amount committed.
    The Dragon’s Lair enables deposit of QUICK against dQUICK.
    Tutorial — Step5 (optional): Stake dQUICK to farm XCASH
    Connect and follow us on our social media to get the latest news:
    X-Cash Website: https://xcash.foundation
    Swap X-Cash in the X-Bank: https://x-bank.io
    Quickswap Exchange: https://quickswap.exchange
    X-Cash Documentation: https://docs.xcash.foundation/applications/wxcash
    Follow Us on Twitter: @XCashCrypto
    [Liquidity Farming] XCASH launch on Polygon + Quickswap was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
    View the full article
  6. Snider
    In this fast-paced and revolutionized world, crypto has taken hold in every field. Therefore, Graft Network wants to provide a better strategy to give everyone easy access to modern technology as well as lead in finance and business.
    Graft Network just updated the mining algorithm to RandomXG which surely it takes the reliability and credibility of the platform to another level. Hence, creating a more secure, decentralized, fast and scalable network. 
    What is Graft Network?
    It is a fully decentralized, transparent and open-sourced blockchain-based electronic payment and processing project. Also, it provides a similar experience like credit card processing network, with the added security of blockchain and decentralized technology.
    Supernodes (SNs) are a type of master node and a foundation of the blockchain, performing off-chain operations like as authorizations, validations, gateway services, support for service brokers, and numerous other activities. They represent the GRAFT Network’s Proof-of-stake layer. Graft Network has 2000 active supernodes and it is all set to revolutionize the world with its impeccable services.
    Why was there a Need of Changing the Mining Algorithm?
    Graft Network changed its mining algorithm from ASIC cryptonight_v7 algorithm to RandomXG algorithm. So, the algorithm is updated and adjusted in order to provide a more decentralized ecosystem and obviously to get rid of Field-Programmable Gate Array (FPGA).
    Previously, one specific user was mining with FPGA for a low price risking the integrity of the platform.  In order to solve the problem, Graft Network has changed the mining algorithm. The new mining algorithm RandomXG is for CPU mining, only.
    The RandomXG algorithm is an algorithm of proof of work and proof of stake that replaces the cryptonight_v7 algorithm. Furthermore, Graft Network has created a platform with a high level of encryption which is geared at systems that prioritize privacy and anonymity. Additionally, the Graft team decided to start from scratch and build a new algorithm, an algorithm that combines the finest features of previous algorithm yet provides a new mining base for Graft Network, in particular. 
    Graft Network does not comprise the safety of its users; it is a 100% safe platform. It is free from high severity and security issues. As a result, the new mining algorithm not only makes the platform safe but it also makes it more decentralized and faster.
    What does the changed Mining Algorithm brings to the Network?
    Graft Network believes in creating a better ecosystem so the new mining algorithm makes the user experience:
    Simpler Quicker Secure Convenient Trusted Transparent Graft Network wants each user to have a unique and amazing experience for which the team is always looking to improve and henceforth, create a platform which is reliable and secure.

    The post Graft Network’s Newly Developed Mining Algorithm is the New Talk of the Town! appeared first on Graft Blockchain.
    View Original Post
  7. Snider
    X-CASH x QUICKSWAP: Liquidity Program — Earn QUICK and XCASH
    Dear Community,
    Today, we are excited to finally announce the X-Cash Liquidity Program in partnership with QuickSwap exchange. In short, you will be able to provide liquidity on the XCASH/QUICK pair, get rewarded with the pool fees and with QUICK provided by Quickswap, and stake dQUICK in the Dragon’s Syrup pool to get more XCASH!
    The program is prepared in partnership between Quickswap and X-Cash, each providing $300k worth of coins to sponsor $XCASH and $QUICK liquidity. With the Dragon’s Syrup, more people will be able to learn about X-Cash and what the project and vision we are trying to put forward.
    Program Details
    Liquidity Mining
    Provide liquidity $XCASH/$QUICK and earn $QUICK in return.
    Reward: $300k worth of $QUICK
    Start Time: September 8th, 2021
    Network: Polygon
    Reward duration: 60 days
    XCASH/QUICK pair: 0x30167fea9499c11795bfd104667240bdac939d3a
    Staking
    Stake $dQUICK in the X-Cash Dragon’s Syrup pool to earn $XCASH.
    Reward: $300k worth of $XCASH
    Start Time: September 8th, 2021
    Network: Polygon
    Reward duration: 60 days
    Contract address: (tbd)
    Participating
    How to get X-Cash on Polygon?
    XCASH (Polygon) contract address: 0x03678f2c2c762dc63c2bb738c3a837d366eda560
    You can get XCASH (Polygon Network) in several ways
    Buy XCASH on regular CEX like Citex, Stex or Hotbit, then send them to an X-Bank account to swap main-chain-XCASH to WXCASH (on Polygon). Complete tutorial here. Buy them directly on Quickswap Exchange (Polygon Network) on the XCASH/QUICK pair. Get QUICK
    First of all, we encourage you to read about QuickSwap native token, QUICK and dQUICK, on this article.
    How to Stake your dQUICK to Compound Earnings with Dragon’s Syrup
    You can get QUICK directly on the QuickSwap Exchange, in the Swap section.
    Add Liquidity on the XCASH/QUICK pool
    Go to https://quickswap.exchange/#/pool and click on “Add Liquidity”. Select QUICK and XCASH (Token address: 0x03678f2c2c762dc63c2bb738c3a837d366eda560). You can also directly find the link to add liquidity here. Select the amount you would like to provide (needs to be equal part QUICK and XCASH), and complete the transaction to get LP tokens. Go to https://quickswap.exchange/#/quick to check the LP farming pool, and look for XCASH-QUICK to stake your LP token. Done! You will get pool reward as well as QUICK reward for the liquidity. Farm XCASH in the Dragon’s Syrup pool
    Go to the XCASH Dragon’s Syrup pool here (link incoming) Enter the amount of dQUICK you desire to stake. Click “Approve dQUICK” to allow QuickSwap to access dQUICK tokens in your wallet and accept the transaction via your Metamask window. Upon confirmation, click “Stake” and use MetaMask to accept the transaction. You will get XCASH in return. Important Link
    X-Cash Website: https://xcash.foundation
    Swap X-Cash in the X-Bank: https://x-bank.io
    Quickswap Exchange: https://quickswap.exchange
    X-Cash Documentation: https://docs.xcash.foundation/applications/wxcash
    Follow Us on Twitter: @XCashCrypto
    X-CASH x QUICKSWAP: Liquidity Program — Earn QUICK and XCASH was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
    View the full article
  8. Snider
    /blog/assets/2020-09-17-monero-0.17-released/oxygen-orion.png Overview
    This is the v0.17.2.3 minor point release of the Monero GUI software. This release contains a decoy selection bug fix that improves privacy.
    The latest CLI release notes can be found on the precedent blog post.
    Some highlights of this minor release are:
    Add payment request functionality to receive page (#3650) Display images on create hardware wallet page (#3618) Reenable password strength meter in release binaries (#3562) Automatically correct incorrectly typed restore dates (#3564) Add tooltips to all buttons (#3490) Add search transactions button on receive and account page (#3216, #3546) Set an unused wallet name in wizard (#3544) Fix bug not accepting new restore height (#3563) Fix get / check proof on Sign / Verify page (#3674) Fix scanning QR codes that miss an URI prefix (#3598) Various date picker improvements Accessibility improvements (#3611, #3603) Minor bug fixes and UI improvements The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 3 people who worked, largely unpaid and altruistically, to put out 170 commits containing 26608 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    selsta luigi1111 rating89us Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 64-bit (Installer) macOS, 64-bit Linux, 64-bit A complete guide for the GUI wallet is included in the archives, but an online version is available.
    Download Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-gui-win-x64-v0.17.2.3.zip, 1ae06f71e7b469ea95f10008f2624797cf0a3223e47f07c42591c0dff63e63ec monero-gui-install-win-x64-v0.17.2.3.exe, 8b5f37eb6b2d0534cbbc490986f23d7fb470697b7839ac1305499c4675f1ea11 monero-gui-mac-x64-v0.17.2.3.dmg, 20fe978294b65c2bb44932489f114e6a91cb4c2c4b03afb87ab683c8182cf811 monero-gui-linux-x64-v0.17.2.3.tar.bz2, f011ba2bd67395ca8c17d5faf1397785905533dd1a8b9ebf1e6810d0f726f40f A GPG-signed list of the hashes is at https://www.getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).
    View the full article
  9. Snider
    /blog/assets/2020-09-17-monero-0.17-released/oxygen-orion.png Overview
    This is the v0.17.2.3 point release of the Monero software. This release contains a decoy selection bug fix that improves privacy.
    Some highlights of this point release are:
    Apply gamma distribution from chain tip when selecting decoys (#7822) Protect wallet from divide by 0 caused by integer truncation (#7846) Ledger: speed up wallet generation, sync, and subaddress generation (#7744, #7745, #7788) Fix optimize-coinbase for p2pool payouts (#7894) Provide key images of spent outputs in wallet rpc (#7839) Support freeze, thaw, and frozen in wallet rpc (#7838) Remove blocked addresses/hosts from peerlist (#7810) Stop adding more outputs than bulletproof allows, split transaction (#7825) Set correct Ledger minimum version (#7789) Fix crash with Trezor passphrase entered on computer (#7781) Update randomx to v1.1.9 (#7734) Fix boost 1.76.0 compatibility (#7736) Fix rescan_bc keep_ki option (#7680) Minor bug fixes The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 16 people who worked, largely unpaid and altruistically, to put out 87 commits containing 838 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    luigi1111 dsc xiphon benevanoff moneromooo anon tobtoht selsta mj-xmr sech1 hyc ndorf woodser ph4r05 j-berman rbrunner7 Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 32-bit macOS, 64-bit Linux, 64-bit Linux, 32-bit Linux, armv7 Linux, armv8 Android, armv7 Android, armv8 FreeBSD, 64-bit Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-win-x64-v0.17.2.3.zip, ba3f4ec7429aacf3e712bdf21d1ceb800eb94e1e376be8b2360a01d88bb862be monero-win-x86-v0.17.2.3.zip, 460ac8722d713022c13970d96f9098eb04b5ca4f59cc9dc929cc2dd590045a1e monero-mac-x64-v0.17.2.3.tar.bz2, e479668f37a623691c75a9e4ec04f69af8fae0faaae5790760eb758f3955b1f7 monero-linux-x64-v0.17.2.3.tar.bz2, 8069012ad5e7b35f79e35e6ca71c2424efc54b61f6f93238b182981ba83f2311 monero-linux-x86-v0.17.2.3.tar.bz2, a93788591bd56753369a3f3171fbefb09387758c1e3a219e9265473031f0a35d monero-linux-armv8-v0.17.2.3.tar.bz2, bbff804dc6fe7d54895ae073f0abfc45ed8819d0585fe00e32080ed2268dc250 monero-linux-armv7-v0.17.2.3.tar.bz2, 9100704b7d98d7bffbf7f72804c0c048f5e60f1dc9f6d4830c633dda3687c419 monero-android-armv8-v0.17.2.3.tar.bz2, 20c32e90c7486bd1fb6948ebb8ee4802be26c902f96b12958429c8aa1c6579b5 monero-android-armv7-v0.17.2.3.tar.bz2, 62f6172e3ebdc1266d5d882b8be4507cb3c8270b92ea6f06330077f6ef4f43e8 monero-freebsd-x64-v0.17.2.3.tar.bz2, 6a2d7ae4303d4eca4fd6df3b230f4624ffa743629e85ad1b0c862326395ca93e A GPG-signed list of the hashes is at https://www.getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).
    View the full article
  10. Snider
    Dear X-Cash community.
    As we are moving forward with negotiations, and with the successful release of the WXCASH, we are able to continue our plan of listings for X-Cash.
    This information has been disseminated already in our chats and discussions with the community, but I think it’s important that we lay it out here for everyone to see.
    DEX Listing & Liquidity Program
    I wanted to share some quick news with you about the liquidity pool as it has been a subject of discussion in the past weeks.
    It should come at no surprise that we will list and provide liquidity incentives on Quickswap exchange. As a native DEX running on the polygon network, it was clear for us to continue to navigate on the polygon network with the WXCASH. This will make it easy for everyone to provide liquidity without paying aberrant fees.
    We will start and focus on Quickswap at first at it will be a perfect introduction into DeFi for WXCASH, but we will be able at a later time to continue on other Polygon available DEX like Sushiswap. Ultimately, our goal is to propose a liquidity pool on Uniswap with the ETH-WXCASH.
    Because we want everyone to have an understanding of what DeFi can offer, and how you can provide liquidity, stake LP tokens, understand farms etc… we will write next week a complete tutorial of what you will be able to do on Quickswap Exchange with your WXCASH. The liquidity pool will follow right after the tutorial, so you will have some time to prepare your tokens, and everyone will have the chance to join.
    CEX Listings
    With the Quickswap DEX pool active, we will be able to quickly follow up on the listing on Centralised Exchanges. Our plan is as follow:
    With the help from the liquidity of the DEX pool, and the trading volume and visibility the project will gain, we will be able to negotiate a great deal for the TIER 2 Exchange listing. Without diminishing the value of the exchanges we are listed on, we believe that the TIER 2 exchanges we are looking at will provide better trading conditions than any of the exchanges we are listed on now. We will follow up quickly with a TIER 1 listing. We will need to finance this listing, and for this, we need liquidity on the market. With the DEX and TIER 2 listing, this should not cause problems and will greatly improve our chances to get listed at a good price. Please be minded that we will probably list the WXCASH instead of regular XCASH, as it will simplify A LOT the listing process with the exchanges. This is a lot of good opportunities for XCASH trading, and this is only made possible thanks to the possibility to wrap XCASH. Without it, we would be able to access the ETH ecosystem, and getting listed on an exchange would be way harder on our native coin.
    DPOPS and developer update
    We have heard the community’s backlash in the past weeks, concerning the lack of direction or management within the leading team. We have discussed and came to a satisfying conclusion with the team, which we believe will unlock a lot of the obstacles that prevented the project to move forward at a satisfying pace. We are looking forward to telling you more once we have finalized this, at it needs its own article, but we think you should be able to feel the changes already.
    Now, our top priority is to put the DPOPS back online, and to pinpoint the exact reason for the instability. We have put in place backup nodes to help restarting, and looking for the fixes while having a running network. We hope to bring back the trust of the delegates that have left the network because of the instabilities.
    All in all, I would like to thank the whole community for their support. As I have explained in some discussions, although the project side seems slow, the developing team keeps motivation as we know what is coming forward, and we believe that the DEX pools and the following CEX listings will help a lot in that regard. We trust you to help us communicate on all the great news that are coming, and spread the word about X-Cash!
    X-Cash Update: Exchange Listing Schedule, Developer Update was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
    View the full article
  11. Snider
    We are happy to announce that the Atomic Swap implementation developed by the COMIT team is mature enough to be used on Monero's network. For now, makers must buy Bitcoin and takers must buy Monero, but anyone can be a maker or taker. It is easier at the moment to sell Bitcoin for Monero than the other way around. To try a swap yourself, download the asb software developed by the COMIT team, follow the instructions and let them know if you find any issues (works also over Tor!). Remember this is brand new technology and might have unexpected bugs. Be careful and only test with small amounts. To find swap providers, visit unstoppableswap.net.
    What are Atomic Swaps?
    Atomic swaps are a way to exchange two cryptocurrencies (in our case Monero and Bitcoin) without relying on a trusted third party (like a cryptocurrency exchange company) and without needing to trust the person on the other side of the swap. These swaps are called "atomic" because they only have two possible outcomes: either the trade is successfully completed and each trader receives the other one's funds, or nothing happens and both traders keep the funds they started with. Since the protocol forces both parties to follow the rules, it is not possible to run away with the other party's coins, which is the main reason trusted third parties are required when exchanging cryptocurrencies.
    Two teams are working on developing Atomic Swaps for Monero:
    COMIT Farcaster (Research funded by the Monero community through the Community Crowdfunding System) View the full article
  12. Snider
    /blog/assets/2020-09-17-monero-0.17-released/oxygen-orion.png Overview
    This is the v0.17.2.0 point release of the Monero GUI software.
    The latest CLI release notes can be found on the precedent blog post
    Some highlights of this release are:
    Allow sending to multiple receipients (#3332) Add support for pruning of new databases in wizard (#3345) Add support for storing multiple remote nodes (#3373) New "Grab QR code from screen" functionality (#3292) Improve search functionality on Transactions page (#3215) Fix a memory leak on Linux (#3326) Fix incorrect fiat price api usage with Kraken (#3298) Enable dns block list in simple mode (#3314) Restrict max window width / height, fix initial window alignment (#3302) Updated translations from Weblate (#3342) Update monero submodule to v0.17.2.0 (#3382) Minor design improvements The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 66 people who worked, largely unpaid and altruistically, to put out 93 commits containing 31902 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    xiphon luigi1111 rating89us toh995 erciccione fsrw42 benevanoff secure-designer selsta A special thanks to translators
    Luis Alejandro Herrera Bolaños, ian vatega, Miguel Medina, Michael Russo, Samuel, 0x82b, kombometralla, Tony Nguyen, Boris Sipos, Tabula Rasa, 8uDD4T, Gleb Golov, Lafudoci, Joan Montané, Nima Ghotbi, Gilberto F da Silva, Russian Bear, Agent LvM, v1docq47, Scott Anecito, x52fws, Lana, Demofrager, Ian appel, EvolBit, Bertrand Jacquin, lir4376, Loué Marie, el00ruobuob, Michal Vašíček, dskch83, ambercookie, warraxxx, Georgios Apostolopoulos, ΚΥΡΙΑΚΟΣ ΚΑΡΑΚΥΡΙΟΣ, Marinus Savoritias, Iason Andreou, Donald A. Iljazi, Vytas, Aivaras Kasperaitis, Renato MB, netrik182, Mathkamy, Allan Nordhøy, obit33, Edwin den Boer, dutchcodes, Ori Levenglick, Yan Abu Arab, G. Orwell, mr, Paul Janowitz, Nicolas, GreenPiece, SJ, Deleted User, Wobole
    Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 64-bit (Installer) macOS, 64-bit Linux, 64-bit A complete guide for the GUI wallet is included in the archives, but an online version is available.
    Download Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-gui-win-x64-v0.17.2.0.zip, 12d7e364b3870b96ed646329634cdcb7e9b2f3fb3290c9834d7a17214d6b47c2 monero-gui-install-win-x64-v0.17.2.0.exe, 2e6150da2243eb887b727fb1e7cd7824ea869648fcd55843f7e767f1966026ab monero-gui-mac-x64-v0.17.2.0.dmg, 8825b196146c73d13292d1e65aa3c263170358af938dc4b47b498fab1d12f0c0 monero-gui-linux-x64-v0.17.2.0.tar.bz2, ee31d67f3df174cc88b01a528aa9d882504fb5f7ae805f449ff35820a4d45bbb A GPG-signed list of the hashes is at https://www.getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).
    View the full article
  13. Snider
    /blog/assets/2020-09-17-monero-0.17-released/oxygen-orion.png Overview
    This is the v0.17.2.0 point release of the Monero software. This release contains bug fixes and daemon stability improvements.
    Some highlights of this point release are:
    Only print blocked nodes once with --enable-dns-blocklist (#7295) Fix Mac serialization compatibility issues (#7350) Fix potential crash with Trezor (#7336) Fix daemon crash with --db-sync-mode fastest (#7362) Daemon stability improvements (#7309, #7390, #7459, #7615, #7621) Bump OpenSSL dependency to 1.1.1k (#7637) Minor bug fixes The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 9 people who worked, largely unpaid and altruistically, to put out 39 commits containing 1146 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    luigi1111 ndorf moneromooo anon selsta mj-xmr sech1 hyc ph4r05 Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 32-bit macOS, 64-bit Linux, 64-bit Linux, 32-bit Linux, armv7 Linux, armv8 Android, armv7 Android, armv8 FreeBSD, 64-bit Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-win-x64-v0.17.2.0.zip, 71e531a0f799c80e3f6319888bd5b85a737091b9bd5d66366cae036163857caf monero-win-x86-v0.17.2.0.zip, c772070ebdfe9e0d6abda5073808e648e69f8c35f8010e66b80f45a6bdb01792 monero-mac-x64-v0.17.2.0.tar.bz2, 2e95dc107ab0dab36f5544bec040180264256e45407c383cfb45cfe328fe42e0 monero-linux-x64-v0.17.2.0.tar.bz2, 59e16c53b2aff8d9ab7a8ba3279ee826ac1f2480fbb98e79a149e6be23dd9086 monero-linux-x86-v0.17.2.0.tar.bz2, e8a39be486549908c10524d851a006c21c30b1a49142586aff0a17e7c4d46077 monero-linux-armv8-v0.17.2.0.tar.bz2, a004fad5348549e2f1610380775353f19db7cbca0cbe4acbfab87832c484da62 monero-linux-armv7-v0.17.2.0.tar.bz2, b5986d6dfbddee14e32b28305dd0dc6352c18b632f569227f2c7265ef7dc5081 monero-android-armv8-v0.17.2.0.tar.bz2, b8a353f02feaee9aae3d279c043ea33a32413a298d8b6122d00a65508f15169d monero-android-armv7-v0.17.2.0.tar.bz2, 815341f7d46f75a8905f8b51932e1034a7f6b1669757ff48224632d08339d1bf monero-freebsd-x64-v0.17.2.0.tar.bz2, 34ef5702a050298f48ccea7db992137bc98c8e6eba45ecd90b47ce0a4b7bf0f8 A GPG-signed list of the hashes is at https://www.getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).
    View the full article
  14. Snider
    On June 5th 2018 Bittrex announced that the BitTube (TUBE) wallet is open and ready for trading. We are happy to share this information with our community. The first available trading pair is BTC/TUBE .
    The Bittrex exchange is a U.S.-based blockchain platform providing real-time trading and industry-leading security. Main issues on Bittrex are security first, robust trading and corporate responsibility.
    Bittrex is committed to comply with U.S. Regulations and for this all crypto currencies listed on Bittrex need to go through a validating process to make sure to be in line with the SEC rules.
    To trade on Bittrex ( https://www.bittrex.com/ ) it is neccessary to register an account on https://www.bittrex.com/account/Register .
    When transfering BitTube to your Bittrex account make sure you are using Wallet ID and Payment ID.
     
    Join our Newsletter!
    Success!
    Email
    SUBSCRIBE!
    Join our Newsletter!

    SUBSCRIBE! You have Successfully Subscribed!
    Labels
    AirTime blockchain company mining Mobile app platform trading updates wallet The latest
    Weekly update 9th of November Weekly update 3rd of November Niffler.co Announces Listing Of TUBE As A Trading Pair Weekly update 26th of October Weekly update 19th of October The post BitTube is listed on Bittrex appeared first on BitTube.

    View the full article
  15. Snider
    We are happy to announce that after months of work, this website is now available in Norwegian!
    Norwegian is the 14th language available for getmonero.org, following English, Spanish, Italian, Polish, French, Arabic, Russian, German, Dutch, Brazilian Portuguese, Turkish, Chinese simplified and Chinese traditional.
    A big thanks to ChrisAvis and the community crowdfunding that made his work possible. Translators like him allow Monero to continue to reach a much larger audience.
    To browse the website in Norwegian, simply select Norsk from the language dropdown menu on the top right, or use this direct link: https://www.getmonero.org/nb-no/index.html
    Do you want to help make Monero available to everybody in the world? Become a translator!
    The Monero wallets, Getmonero and other content are open for translation on Weblate, our self-hosted translation platform. If you need info, support, or you just have questions, contact the Monero Localization workgroup.
    View the full article
  16. Snider
    Hello, everyone! I know you are super excited about the possibility to swap XCASH to wXCASH and vice-versa, so I’d like to share a bit of information on the wXCASH project status.
    What’s wXCASH about?
    In a few words, it’s a token built on top of ERC-20 / BSC protocols that allows our project to scale up even more by targeting top exchange listings. The token will have a value of 1:1 to XCASH.
    So what’s the X-Bank part?
    X-Bank will provide the solution as a service and user interface to swap the coins seamlessly. To achieve this, the following components are being implemented:
    wXCASH Hot/Cold wallets infrastructure + ETH / BSC nodes; Multiple accounts for each user (1 XCASH & 1 wXCASH); wXCASH account currency support: each user will have an ERC-20 / BSC account to deposit and withdraw tokens; The swap logic: users will be able to swap the coins between their accounts only; wXCASH deposits and withdrawals processing; No commission or fees will be applied for any user operations — swapping or depositing/withdrawing. Instead, a minimum threshold e.g. 5M XCASH per withdraw will be set up. This is not the whole list because some technical parts are being reworked and will be communicated later on.
    What’s done?
    I’ll be short here:
    X-Bank Backend part is fully completed: multiple accounts support, handling different currencies, sync logic reworked and improved, and the “swapping” logic is completed and fully tested. ETH / BSC nodes are ready and synced, and test contracts are created and deployed to the chains. Hot- and cold- wallets for wXCASH and deposit processing is done but not fully tested. What’s left?
    X-Bank Frontend and iOS App: user interfaces for multiple accounts management and the swap page are being worked on. ERC-20 / BSC deposits are being tested, withdrawal functionality is being implemented. At the moment, the contracts are deployed to the Ropsten and Binance testnets only. When all the tests pass, contracts will be run on the main network. wXCASH on ETH versus BSC
    BSC (Binance Smart Chain) is a fork of the Ethereum chain. Ethereum virtual machine (EVM) runs perfectly on the BSC, as well as Ethereum smart contracts and dApps work with ease. So from a technical and integration point of view, there is no difference in which chain we run wXCASH on.
    Ethereum is more popular and widely adopted, but fees are extremely high; BSC is EVM compatible, and fast. Fees are lower but fewer users are familiar with BSC and how to use it; Exchange listing is a bit easier for ETH tokens rather than BSC. So ETH or BSC?
    The question is not answered yet but we’ll take into account all the pros and cons and try to find the best solution.
    P.S. iOS App work is on a separate track and might become available later than X-Bank Frontend implementation. This way it will not block the launch of the wXCASH swap.
    P.P.S. A closed beta test is targeted for this month, stay tuned to get updates on it!
    Thank you.
    X-Bank wXCASH update. was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.

    View the full article
  17. Snider
    Dear X-Cash community,
    Today, we are glad to officially starts the builder’s program initiative. We have tried and iterated for a while, and are now happy with the workflow we have found to enable you to help the project and participate in its development.
    What is the builder’s program?
    The Builder’s program is an initiative to enable a community member to either:
    Apply to a community funded project and help to develop a necessary tool for the X-Cash Foundation, while being retributed for the task (that we call RFC — Request For Contributions) Propose a project that you want to do or looking for a community member to do, and looking to get funding for (an RFF — Request For Funding). With the contributor program, we will use the community funds to help and promote these projects and participate in their funding.
    How does it work?
    You have an idea of a project that you know will help the project? You can easily propose a project in the Builder’s Program repository: https://github.com/X-CASH-official/builders-program
    To propose a new project, go to Issues and create a new issue.
    Then, chose to create the issue using the BP Proposition template.
    Give it a title and, and follow the template to describe the project scope.
    Please be aware that we will not review incomplete or rushed propositions.
    Type
    Request For Contribution (RFC): You have a project in mind but looking for a contributor to do it. You are ready to participate in the funding.
    Request For Funding (RFF): You have a project in mind and want to do it. You are asking for funding from the community fund or the community.
    Description
    Describe the project in details, and why you believe it is needed for the X-Cash project.
    Prerequisites
    Explain the necessary skills needed to successfully complete this task. If you plan to undertake the project you are proposing, you will be expected to give references on why/how you can successfully complete it.
    Milestones / Deliverables
    Explain the different steps of the project and the expected timeline. As much as possible, please describe intermediary steps and the list of deliverables. It will help us decide together what we expect as a finished product.
    Additional information / Budgeting
    Talk about the expected difficulties that you might encounter, as well as budgeting and a detailed description of the different expenses to support your application.
    You can either use XCASH or USD, but the USD/XCASH rate will be taken at the beginning of the project.
    Example: Successfully completed and paid to Snakewaypasser, the Android wallet program was the first project to help us iterate on the Builder’s program. You can use it as an example of what we are expecting for a complete BP project proposal:
    Where to see the projects?
    The BP project proposals will be listed on the Builder’s Program repository and on the xcash.foundation website under the contribute section.
    Open, ongoing and finished builder’s project will appear on the https://xcash.foundation website.Make sure to 👁‍🗨 Watch and to ⭐Star the repository to not miss any new project!When to start?
    You can start right now! We have been listening, and we know that there are a lot of ideas floating about and that people want to participate in the project but didn’t have the right framework to do so. So if you have a project or an idea that you believe would serve the X-Cash ecosystem, do not hesitate to propose for our review!
    We will soon post our own community funded project, so keep an eye out! 👀
    Once again, we want to thank everyone for their unwavering support. Let’s build the next technological revolution together 💪
    Builder’s Program was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
    View the full article
  18. Snider
    Dear X-Cash community,
    Today, we are glad to officially starts the builder’s program initiative. We have tried and iterated for a while, and are now happy with the workflow we have found to enable you to help the project and participate in its development.
    What is the builder’s program?
    The Builder’s program is an initiative to enable a community member to either:
    Apply to a community funded project and help to develop a necessary tool for the X-Cash Foundation, while being retributed for the task (that we call RFC — Request For Contributions) Propose a project that you want to do or looking for a community member to do, and looking to get funding for (an RFF — Request For Funding). With the contributor program, we will use the community funds to help and promote these projects and participate in their funding.
    How does it work?
    You have an idea of a project that you know will help the project? You can easily propose a project in the Builder’s Program repository: https://github.com/X-CASH-official/builders-program
    To propose a new project, go to Issues and create a new issue.
    Then, chose to create the issue using the BP Proposition template.
    Give it a title and, and follow the template to describe the project scope.
    Please be aware that we will not review incomplete or rushed propositions.
    Type
    Request For Contribution (RFC): You have a project in mind but looking for a contributor to do it. You are ready to participate in the funding.
    Request For Funding (RFF): You have a project in mind and want to do it. You are asking for funding from the community fund or the community.
    Description
    Describe the project in details, and why you believe it is needed for the X-Cash project.
    Prerequisites
    Explain the necessary skills needed to successfully complete this task. If you plan to undertake the project you are proposing, you will be expected to give references on why/how you can successfully complete it.
    Milestones / Deliverables
    Explain the different steps of the project and the expected timeline. As much as possible, please describe intermediary steps and the list of deliverables. It will help us decide together what we expect as a finished product.
    Additional information / Budgeting
    Talk about the expected difficulties that you might encounter, as well as budgeting and a detailed description of the different expenses to support your application.
    You can either use XCASH or USD, but the USD/XCASH rate will be taken at the beginning of the project.
    Example: Successfully completed and paid to Snakewaypasser, the Android wallet program was the first project to help us iterate on the Builder’s program. You can use it as an example of what we are expecting for a complete BP project proposal:
    Where to see the projects?
    The BP project proposals will be listed on the Builder’s Program repository and on the xcash.foundation website under the contribute section.
    Open, ongoing and finished builder’s project will appear on the https://xcash.foundation website.Make sure to 👁‍🗨 Watch and to ⭐Star the repository to not miss any new project!When to start?
    You can start right now! We have been listening, and we know that there are a lot of ideas floating about and that people want to participate in the project but didn’t have the right framework to do so. So if you have a project or an idea that you believe would serve the X-Cash ecosystem, do not hesitate to propose for our review!
    We will soon post our own community funded project, so keep an eye out! 👀
    Once again, we want to thank everyone for their unwavering support. Let’s build the next technological revolution together 💪
    Builder’s Program was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.

    View the full article
  19. Snider
    Dear community,
    In accordance with our statement on September 13th, 2020, we are providing you with an update on the buyback of XCASH from X-Network.
    https://medium.com/x-cash/announcement-x-cash-buy-back-6083451f97f
    Between September 16th, 2020 and December 20th, 2020, we have acquired a total of 823,298,490 XCASH to our initial inventory of 10Billions XCASH. These funds have been added back to the company’s address (X-Network Inventory Fund) and can be verified with its reserve proof on the Segregated Funds page.
    With this buyback, our objective is to support the price and confirm our commitment, after 2 years and a half of hard work, to make X-Cash a successful project.
    The funds will remain locked and be used later on to support the growth of the project. These initiatives will include:
    - Liquidity program for market-makers
    - Grant to the foundation to support development
    - Exchange listing contributions
    - Support the X-Cash Foundation’s infrastructure & marketing costs
    On behalf of all the contributors, I would like to thank you for the support throughout the years. We will keep on working towards developing great technology and reinforcing our communities thanks to the various initiatives we have started in the past months.
    Guilhem
    X-Network Buy Back was originally published in X-CASH on Medium, where people are continuing the conversation by highlighting and responding to this story.
    View the full article
  20. Snider
    I recently came across a bounty in the TRTL Discord for an article about TurtleCoin. The requirements were loose, it was mainly just a length requirement, so I figured I’d brew up some coffee and give it a shot.
    Thanks to Keda666 for reminding me to post this.
    Starting a coin network is easy. Taking care of one, helping it grow, keeping it healthy, giving it good guidance — those are the hard parts. My name is RockSteady, and TurtleCoin is my problem child.
    With an introduction like that, you might be thinking that I regret creating TurtleCoin or that it is a mistake in the sense that it was a failure, but quite the opposite as Bob Ross might say. TurtleCoin was created at the height of the crypto-boom of December 2017. At the time you could create literally anything, put “crypto” in the name, and sell it for millions, even if it didn’t exist (RIP BitConnect, never forget).
    Out of the plethora of networks that were coming out, a little privacy category emerged. You had DASH and the masternode networks, you had Zcash with the optional privacy networks, then you had Bytecoin, Monero and the rest of the Cryptonote family with stealth addresses and fulltime privacy… and off standing in the corner, struggling for attention and trying to peer above the shoulders of the Cryptonote family is little TurtleCoin with a pizza stained shirt and light coating of Pabst Blue Ribbon.
    As you may or may not know, TurtleCoin was a fork of Bytecoin. Incidentally, TurtleCoin and Monero for the first 3 years shared the same codebase, which came from an old retired version of Bytecoin. The way the privacy works in TurtleCoin and Monero is that if you think of every transaction as a handful of coins and dollars, each coin or dollar is matched up with a handful of others on the network and spent in a way that an observer can’t tell whose coins participated in the transaction, and nobody can scope out your transaction history or balance without being given keys to see it.
    So, big deal, right? You fork some code, then change all the mentions to the old guys, throw in a little pizzaz, maybe some ninja turtle memes, and boom you’re off to the races, right? Shitcoin starter pack.
    Unfortunately that is mostly true for some networks, at least to get the coin off the runway and into the sky. It takes almost zero work to fork code, change some variables and launch a network, but if the hundreds of projects people created based on our code are any indicator, it takes much much more than that to keep a network functioning and thriving.
    Lets get to the problem child part.
    A big reason why none of these forked networks exist anymore is that your network is like a little pot of gold, always out of reach, but for those smart enough you can find ways to make things easier as miner, or when all else fails, make things harder for everyone. Over the years, through the system of mining coins alone, we have seen it all with regards to the measures people will take to overcome the rules of the network to drive up their profit just a few points while having disastrous effects for the rest of us.
    At times we have seen people forging timestamps for mined blocks, pulse mining the network to skew the difficulty enough so that many coins are produced in an hour, then when the difficulty climbs as a result, the miner leaves for another network with lower difficulty and leaves us to mine slow blocks for an hour before they return as the difficulty goes back to normal. Wash, rinse repeat. We even saw people so bold as to incorporate TurtleCoin as the payload of botnets, presumably to get more mining power.
    Miners and their grubby little hands were the least of our troubles, along the way we noticed bugs that either got exploited and created a fire that we had to put out (like the fusion spam), or bugs that hadnt yet been exploited luckily (like the remote RPC bug). Sometimes when you fork code from others, this is the risk you take.
    Maybe it is getting clearer why we don’t have as many TurtleCoin forks around anymore. If it isn’t so clear, here is an analogy — If you put a plane in the air, and stop refueling it, it will eventually touch the ground.
    With all of these problems, TurtleCoin still prevails, and has not to this day had a single attack on the protocol that caused a loss of funds from any user, and with a pot of gold at the end of the rainbow as big as the remaining emission, nobody has exploited that either. (at the time of this writing, TurtleCoin still has 91% of the supply left to be mined)
    Three years later, TurtleCoin still receives new code every day, new features, improvements, fixes — and still has users transacting despite the price being the lowest it has ever been in history. During these three years, as a team we have seen hundreds of networks spawn from the TurtleCoin code. These networks may have been other peoples hopes and dreams, Id imagine.
    “Finally this will be the one” some of the forkers might say, before they sell off their entire premine and start the next project.
    Today I can think of two networks that forked us that are still functioning, and of those two, when I think of how many receive software updates, Id have to say it is maybe one that is still actively developed.
    As we round our way into the second era of TurtleCoin, the one where we scrap all code and write something new from scratch, I hope some of this funny business in the markets changes, and I do hope that all the forkers out there get their act together, however irrational they may be. TurtleCoin is our hopes and dreams, our pot of gold, our problem child. TurtleCoin is actively developed and every bit as serious of a project as others, it just has a funny name.
    Accept no imitations, TurtleCoin is here to stay. When you think privacy, utility, and low cost transactions without showing the world your balance, think TurtleCoin. When you think about TurtleCoin, think about us, your captains, and a team that wont let you down no matter what the price.
    Thanks for listening, I hope you all stick with us for TRTL v2.. its a game changer in the works. No more mining, even better privacy, everything new. Get some while you can, don’t say we didn’t warn you.
    Originally published at TurtleCoin.

    View the full article
  21. Snider
    Hey y’all, 

    This week has been the first week back after the Christmas holidays, so our dev updates will be back to their usual length from here on out. This week, the Session team worked to finish the final Session protocol implementation, specifically focusing on closed groups. The Lokinet team submitted their TUN refactor code which is expected to improve performance, especially on Windows. The Loki Core team worked on various Oxen rebranding projects, mostly focusing on the wallets. 

    Loki Core 

    Add API for staked amount on pending transactions https://github.com/loki-project/loki-core/pull/1386 Strip Android libs, disable Trezor & protobuf https://github.com/loki-project/loki-core/pull/1388 Backport Oxen rebranding from dev branch https://github.com/loki-project/loki-core/pull/1387  Fix Windows CLI bug https://github.com/loki-project/loki-core/pull/1385  Update electron wallet file name https://github.com/loki-project/loki-core/pull/1384  Update dependencies https://github.com/loki-project/loki-core/pull/1383  iOS and Android package upgrades https://github.com/loki-project/loki-core/pull/1382 Add optional stake amount calculation to RPC https://github.com/loki-project/loki-core/pull/1381 Oxen rebranding https://github.com/loki-project/loki-core/pull/1380  Lokinet 

    This past week, Lokinet development resumed with significant work on a big “TUN refactor” PR (fTUN is the name of the programmable virtual network interface driver that Lokinet uses to provide local virtual addresses). This throws away a big chunk of borrowed code in favour of a streamlined implementation, which is always nice, but more importantly it fixes a longstanding issue with Windows performance where we have continually seen considerably worse throughput and latency numbers on Windows compared to Linux or macOS. We still have more testing and some known issues to stamp out, but we hope to get release 8.1.3 out, particularly for Windows users, in the near future.

    TUN code refactor https://github.com/loki-project/loki-network/pull/1495 macOS build instruction fixes https://github.com/loki-project/loki-network/pull/1506 Add full-static-deps armhf build (+upload) https://github.com/loki-project/loki-network/pull/1505  Session

    We’re finishing off the remaining Session Protocol changes this week. This primarily means changing closed groups to use the Session Protocol instead of our implementation of sender keys.

    Session iOS 

    Fix bug where attachments would sometimes not download https://github.com/loki-project/session-ios/pull/330  Full Session V2 protocol implementation https://github.com/loki-project/session-ios/pull/325  Reorganise files https://github.com/loki-project/session-ios/pull/331 Full list of commits can be found here https://github.com/loki-project/session-ios/commits/dev  Session Android 

    Core refactor ongoing https://github.com/RyanRory/loki-messenger-android/commits/refactor Session protocol V2 implementation https://github.com/loki-project/session-android/pull/396 Full list of commits can be found here https://github.com/loki-project/session-android/commits/dev Session Desktop

    WIP closed group changes https://github.com/loki-project/session-desktop/pull/1424 Fix conversation message list https://github.com/loki-project/session-desktop/pull/1423  Add tests for Session protocol https://github.com/loki-project/session-desktop/pull/1421 Improve message polling for open groups https://github.com/loki-project/session-desktop/pull/1419 Fix issues with voice recording for voice messages https://github.com/loki-project/session-desktop/pull/1417  Thanks,  

    Kee 

    The post Weekly Dev Update #133 appeared first on Loki.
    View the full article
  22. Snider
    Overview
    This is the v0.17.1.9 minor point release of the Monero GUI software. This is a recommended release that contains mitigations against the ongoing memory exhaustion attack.
    The latest CLI release notes can be found on the precedent blog post
    Some highlights of this minor release are:
    Update monero submodule to v0.17.1.9 Windows GUI binary is now reproducible Add high DPI support on Windows The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 3 people who worked, largely unpaid and altruistically, to put out 12 commits containing 99 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    xiphon Snipa selsta Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 64-bit (Installer) macOS, 64-bit Linux, 64-bit A complete guide for the GUI wallet is included in the archives, but an online version is available.
    Download Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-gui-win-x64-v0.17.1.9.zip, 862aa9a6564a60be3e70ee30eb061d5186a141ce62842b3d741558470c255988 monero-gui-install-win-x64-v0.17.1.9.exe, edc47b1540510640a40e8d52ad4ab3a6220f935e881fd65b02ccce94a28c3fa2 monero-gui-mac-x64-v0.17.1.9.dmg, c8a8ea012e8731bfacd17434fdd3a0f03302fc61d7187d218da5ff6a6e869f0b monero-gui-linux-x64-v0.17.1.9.tar.bz2, 6334acbe9877e2e86b1902b111abc59e170aedc701ea71cbae49830191bbd745 A GPG-signed list of the hashes is at https://getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

    View the full article
  23. Snider
    Overview
    This is the v0.17.1.9 minor point release of the Monero software. This is a recommended release that contains mitigations against the ongoing memory exhaustion attack.
    Some highlights of this minor release are:
    Add different limits for epee binary format for P2P and RPC Add more sanity checks on data size (portable_storage) Fix deadlock banning while updating peer lists Add aggressive restrictions to pre-handshake p2p buffer limit Add a max levin packet size by command type Restrict duplicate keys and unnamend sections in epee binary format More sanity checks in new chain block hashes Minor bug fixes The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 7 people who worked, largely unpaid and altruistically, to put out 30 commits containing 362 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    luigi1111 Snipa moneromooo vtnerd selsta xiphon binaryFate Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 32-bit macOS, 64-bit Linux, 64-bit Linux, 32-bit Linux, armv7 Linux, armv8 Android, armv7 Android, armv8 FreeBSD, 64-bit Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-win-x64-v0.17.1.9.zip, a3e6e2f55deb487f6b4a33cf430d82d62e986d37d7d589dcb33a4ff0a13a062b monero-win-x86-v0.17.1.9.zip, bb3c633a3d8ac160bc9c75ef514a9cbc77f1f45bdbd220d1963d78d66435c23a monero-mac-x64-v0.17.1.9.tar.bz2, d4850ae45eee67868140183cd8c00f9e1f9e1cc5e415b00bc78c14c7bab85834 monero-linux-x64-v0.17.1.9.tar.bz2, 0fb6f53b7b9b3b205151c652b6c9ca7e735f80bfe78427d1061f042723ee6381 monero-linux-x86-v0.17.1.9.tar.bz2, 1f51206c1996a577f976c0526b93cc495fe577db21f68b55636dce926f201206 monero-linux-armv8-v0.17.1.9.tar.bz2, ef16c3aefc8a17f0a547ffec9e2f087923c6bf293b9538294d14cbd318f1ab98 monero-linux-armv7-v0.17.1.9.tar.bz2, c8b226af900b018fade24742e5936b0ef6cec3fcdbc8a57a4b3f3d6d2507a2ec monero-android-armv8-v0.17.1.9.tar.bz2, 2c45e0fb364ff2e60aa9cdf0d3faef145b22a8632b3336cc248eeba24352d39b monero-android-armv7-v0.17.1.9.tar.bz2, c7192caf85f82ecdd1e7299c9ae6314fe2fb02ed9b7035a426a8644b676cc75f monero-freebsd-x64-v0.17.1.9.tar.bz2, 3052f691a1a7631ba50c3f4d6f1b1355bdcc9a8c0c617cf56ced400afa1ea402 A GPG-signed list of the hashes is at https://getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

    View the full article
  24. Snider
    /blog/assets/2020-09-17-monero-0.17-released/oxygen-orion.png Overview
    This is the v0.17.1.9 minor point release of the Monero software. This is a recommended release that contains mitigations against the ongoing memory exhaustion attack.
    Some highlights of this minor release are:
    Add different limits for epee binary format for P2P and RPC Add more sanity checks on data size (portable_storage) Fix deadlock banning while updating peer lists Add aggressive restrictions to pre-handshake p2p buffer limit Add a max levin packet size by command type Restrict duplicate keys and unnamend sections in epee binary format More sanity checks in new chain block hashes Minor bug fixes The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 7 people who worked, largely unpaid and altruistically, to put out 30 commits containing 362 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    luigi1111 Snipa moneromooo vtnerd selsta xiphon binaryFate Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 32-bit macOS, 64-bit Linux, 64-bit Linux, 32-bit Linux, armv7 Linux, armv8 Android, armv7 Android, armv8 FreeBSD, 64-bit Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-win-x64-v0.17.1.9.zip, a3e6e2f55deb487f6b4a33cf430d82d62e986d37d7d589dcb33a4ff0a13a062b monero-win-x86-v0.17.1.9.zip, bb3c633a3d8ac160bc9c75ef514a9cbc77f1f45bdbd220d1963d78d66435c23a monero-mac-x64-v0.17.1.9.tar.bz2, d4850ae45eee67868140183cd8c00f9e1f9e1cc5e415b00bc78c14c7bab85834 monero-linux-x64-v0.17.1.9.tar.bz2, 0fb6f53b7b9b3b205151c652b6c9ca7e735f80bfe78427d1061f042723ee6381 monero-linux-x86-v0.17.1.9.tar.bz2, 1f51206c1996a577f976c0526b93cc495fe577db21f68b55636dce926f201206 monero-linux-armv8-v0.17.1.9.tar.bz2, ef16c3aefc8a17f0a547ffec9e2f087923c6bf293b9538294d14cbd318f1ab98 monero-linux-armv7-v0.17.1.9.tar.bz2, c8b226af900b018fade24742e5936b0ef6cec3fcdbc8a57a4b3f3d6d2507a2ec monero-android-armv8-v0.17.1.9.tar.bz2, 2c45e0fb364ff2e60aa9cdf0d3faef145b22a8632b3336cc248eeba24352d39b monero-android-armv7-v0.17.1.9.tar.bz2, c7192caf85f82ecdd1e7299c9ae6314fe2fb02ed9b7035a426a8644b676cc75f monero-freebsd-x64-v0.17.1.9.tar.bz2, 3052f691a1a7631ba50c3f4d6f1b1355bdcc9a8c0c617cf56ced400afa1ea402 A GPG-signed list of the hashes is at https://www.getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).
    View the full article
  25. Snider
    /blog/assets/2020-09-17-monero-0.17-released/oxygen-orion.png Overview
    This is the v0.17.1.9 minor point release of the Monero GUI software. This is a recommended release that contains mitigations against the ongoing memory exhaustion attack.
    The latest CLI release notes can be found on the precedent blog post
    Some highlights of this minor release are:
    Update monero submodule to v0.17.1.9 Windows GUI binary is now reproducible Add high DPI support on Windows The complete list of changes is available on GitHub, along with the source code.
    Contributors for this Release
    This release was the direct result of 3 people who worked, largely unpaid and altruistically, to put out 12 commits containing 99 new lines of code. We'd like to thank them very much for their time and effort. In no particular order they are:
    xiphon Snipa selsta Download
    The new binaries can be downloaded from the Downloads page or from the direct links below.
    Windows, 64-bit Windows, 64-bit (Installer) macOS, 64-bit Linux, 64-bit A complete guide for the GUI wallet is included in the archives, but an online version is available.
    Download Hashes
    If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:
    monero-gui-win-x64-v0.17.1.9.zip, 862aa9a6564a60be3e70ee30eb061d5186a141ce62842b3d741558470c255988 monero-gui-install-win-x64-v0.17.1.9.exe, edc47b1540510640a40e8d52ad4ab3a6220f935e881fd65b02ccce94a28c3fa2 monero-gui-mac-x64-v0.17.1.9.dmg, c8a8ea012e8731bfacd17434fdd3a0f03302fc61d7187d218da5ff6a6e869f0b monero-gui-linux-x64-v0.17.1.9.tar.bz2, 6334acbe9877e2e86b1902b111abc59e170aedc701ea71cbae49830191bbd745 A GPG-signed list of the hashes is at https://www.getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.
    Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).
    View the full article
×
×
  • Create New...