PIVX v5.3.2 wallet has been released and is now available for download.

This is an important release that fixes a forking scenario where the node rejects and marks a valid block as invalid in a parallel branch.
We recommend everyone to update your node/wallet as soon as possible to not be affected by this issue.

More info: https://pivx.org/news/pivx-v5-3-2-core-wallet-has-been-released

That depends on Your , our contribution. Don't sit and wait. Share and Care and be thankfull for the gains after the community efforts.

Have a look at Cryptocompare and share your updates there as well.  https://www.cryptocompare.com/coins/pivx/forum/USDT

Hello there,

I recently signed up and tested uploading some files to Skynet and I'd like to know: how do I set a custom timer for auto-deletion of my uploaded files?

I'd like to set some customized auto-deletion timers for my files such as 3 years, 5 yrs, 10 yrs etc.

Is it possible to do it considering the current version of Skynet's protocol?

How do I do it?

Is it planned to be implemented soon?

PIVX SHIELD Testnet Wallet Release

The long-awaited PIVX pre-5.0 testnet release for upcoming 5.0 with SHIELD is now available for download!

This test release includes our new SHIELD protocol that provides the ability to both send and receive shielded transactions that fully protect your transaction data over the blockchain.

SHIELD also sports some unique enhancements such as multi-note shielded spending, a full byte encrypted memo functionality in the Qt wallet, and more.

We encourage everyone to try out this test release and will be greatly appreciated if any issues seen are reported either in the #pivx_testnet PIVX Discord channel, or directly on PIVX GitHub.

Download Latest pre-5.0 Test Release (as of posting = v4.9.99 TR2)
https://github.com/PIVX-Project/PIVX/releases

Notes
1. You must run the wallet with -testnet parameter (or testnet=1 in pivx.conf) for it to connect to the testnet blockchain.
2. A set of parameter files need to be copied onto the system separately. So please take a read of the release notes to know how this is done or ask for assistance in #pivx_testnet channel.
3. Hard fork on testnet will occur at block height 1873550 (approx. Dec. 9th 20:00 GMT)
4. Official Testnet Block explorer:  https://blockbook-testnet.pivx.link/

More Info in our official announcement:
https://pivx.org/news/pivx-shield-is-coming-to-public-testnet

Public Testnet Wallet Page:
https://pivx.org/testnet

thanks again to the Devs for the new release - now working like charm with a 40k tx dust attack - GOOD WORK!!!!!!!!!
 

Download (v2.13.2.7-4e1e6e83f @ 2020-11-24)



new Release is out since 24.11.2020



https://blackcoinmore.org/


updated article about Dust Attacks
https://blackcoin.nl/a-dust-attack-affected-legacy-blackcoin-clients-in-late-sept-2020/




many thanks to the Devs!

It is important that people upgrade/migrate to Blackcoin More v2.13.2.6 and (optionally) raise the fees to avoid relaying these transactions. We will have to raise the fees in the next version to mitigate these attacks

Next More version will be v2.17.0 and is based on BTC Core code 0.17.



Hi, thanks there is progress to the dust attack. Since my first post it stopped for some days but now the attacks are back, daily.  Wallet size bloasts up and working time too.

Therefore i kindly ask how far is the progress with the upcoming 2.17 More release?

thx





More can be downloaded from https://blackcoinmore.org

Thanks

Upcoming Major Riecoin 0.20 Upgrade

A new major Riecoin upgrade is planned, and includes a hard fork. I worked on it during the last few weeks.

The first step of this upgrade was to update the base code to Bitcoin's 0.20, which is done. You can find the experimental code at the Github repository. I also built experimental binaries. Despite their prerelease status, they should work fine and be fully compatible with current 0.16 nodes, though please backup your wallets if you plan to use 0.20, just in case. Feedback is welcome!

Pool operators and other advanced Riecoin users should start looking into the changes and update their software accordingly, as well as closely follow the Riecoin Core development.

Here is a list of notable changes from 0.16.3.1.

• There were inconsistencies regarding the nTime and nBits positions in the Block Header. For example the SubmitBlock and GetBlockHeader commands were inconsistent regarding this. This is now fixed, with nTime always coming before nBits like for Bitcoin. Internally, when hashing for mining or to get a block hash, nBits must still come before nTime (I really don't know what Gatra did, this swap was just unnecessary). Riecoin related software should be updated accordingly. This includes rieMiner, which current stable version is no longer compatible with 0.20, but the latest source code is;
• Testnet was reset. I only know about 2 active Testnet nodes, and both forked for some reason, so it was clear that a fresh start was needed. Additionally, the constellations for Testnet are no longer sextuplets, but quadruplets, and the minimum Difficulty was raised to 600 rather than 304. Testnet nodes are needed, as well as continuous spare mining power to mine test blocks and make Testnet a decent simulation of Mainnet. Please use the Testnet bootstrap found here;
• The "getnetworkhashps" command was replaced by "getnetworkminingpower" (and fixed: previously it only relied on the current Difficulty, now it works properly with lookup blocks). A new metric is used, and is standardized such that 1 correspond to mining a minimum difficulty block (Difficulty 304 in Mainnet or 600 in Testnet) every 150 s. For now it is proportional to the Difficulty^(constellationLength + 2.3), in accordance to observations with rieMiner; the formula may be improved later at any time. The Block Proofs/Chainwork are also now using a similar calculation;
• The GetBlockTemplate's "primes" field is replaced by "constellations", which gives a list of accepted constellations for mining rather than just a constellation size. The "segwit" rule is now mandatory;
• The "getprimes" RPC call is replaced by "getresult" and gives directly the base prime number, instead of all the prime numbers. It will be completed later to include information about the PoW;
• Generated addresses are now Bech32 by default;
• The RegTest is now properly implemented (the PoW here is simply prime numbers). Most of the test units were ported to Riecoin;
• And of course, all the Bitcoin features and bug fixes since 0.17 are now included in Riecoin. Read the Bitcoin Core change logs for more information.

The base code upgrade is pretty much done, though some help is still needed in order to complete the build system and the test units.

No seed node nor DNS seed node IP were hardcoded yet, so one needs to add nodes in the riecoin.conf (there is a template in the binaries page). Please support the network by providing reliable Riecoin nodes and DNS seeders for the long term and share them for hardcoding! This will make initial sync possible without having to add some nodes in the configuration file.

The next step will be the hard fork, in order to improve Riecoin in multiple ways. Early discussions took place here, as well as in Discord and a few posts here somewhat far in the past. Here are planned changes.

• The constellation pattern will be changed from sextuplets to septuplets (quintuplets in Testnet). Both possible patterns will be accepted, so the blockchain will provide more diverse results. One of them will have a chance to be a 8-tuple or longer, which would help a lot to beat records and improve the Riecoin's scientific usefulness. In contrast, the sextuplets cannot be part of longer tuples, which is really a shame. Moreover, longer constellations are also better because they make verification even easier in comparison to finding them, which make them more practical as PoW;
• The SuperBlock system will be removed. While records have indeed been broken this way, it also has significant drawbacks, like freezing the network during an hour every week and a complicated implementation that also confuses a lot of people;
• The Difficulty Adjustment Algorithm will be improved. No particular algorithm has been chosen yet. The chosen one should not be too complicated to implement, while improving resistance to attacks like Selfish Mining or Timestamp Manipulations, proposing smooth Difficulty updates (often enough and without sudden variations) and well respecting the 2.5 minute average for the long term. The discussion is open and DAA Suggestions are welcome!
• The nOffset encoding will be updated in order to allow offsets > 2^256, which allows more efficient mining. Some PoW information like the constellation type may also use this field. See a former rieMiner's developer suggestion about this.

Once the development is advanced enough, a date will be chosen for the hard fork. Testnet will be hardforked first to ensure the well functioning of the implementation (that is also why a proper Testnet network is needed). Stay tuned!

By the way, I am thinking about creating a new BitcoinTalk topic with updated first post (it is clear that Gatra will never come back to update the post, and having outdated information in such an important post does not give a good image of Riecoin and is a source of confusion), and will proceed soon unless some community members are opposed to this.

Bit of a late update here but 4.1 rc1 was released last week and is available for everyone to try / test.

https://github.com/PIVX-Project/PIVX/releases/tag/v4.1.0rc1

As mentioned in the previous dev update above, this new release uses around 900 MB of RAM instead of 2.6 GB!
Also has tons of UI/UX improvements, much faster and smoother network sync, better overall performance etc.
Testing has been going well with many minor issues being addressed before its final release possibly next week!

Once 4.1 Final has been released, will update here.

The Blackcoin More client has been updated to v2.13.2.5!

Please check out our blog article for specific upgrade info. https://blackcoin.nl/blackcoin-more-client-v2-13-2-5/

Then download the files from https://blackcoinmore.org/
$BLK #Blackcoin

I am getting this for BlackCoin More wallet. How can I solve this? Thanks

Unable to bind to 0.0.0.0:15744 on this computer (bind returned error An attempt was made to access a socket in a way forbidden by its access permissions.  (10013))

@coinwider because Coincheck and Binance have voted for delegates with the huge assets of their Lisk cold wallets (ca. 12.5m LSK Coinbase and 5.3m LSK Binance).
Afaik Coinbase voted only for Elite, Binance for all 101 delegates. So they cash up the majority of rewards now (see here), while only breadcrumbs are left for smaller voters.
Another "milestone" of the "awesome" Lisk DPos system. 🤘💩

Factom Rising From the Ashes - 61% UP in Just 7 days - https://www.publish0x.com/crypto-chart-wizard/factom-rising-from-the-ashes-61-percent-up-in-just-7-days-xodvoy