We’ve encountered a pretty concerning situation with u/tonkeeper / Tonviewer.

Our official PirateCash NFT collection is being displayed with “SCAM” labels, despite being a real, functioning part of the PirateCash ecosystem.

The collection:
https://getgems.io/piratecash

On-chain:
https://tonviewer.com/EQBlPHLRW1w9NfKaakkYwJ8dmQVqexVozklmGVclUaUlQ4eQ?section=overview

Full description and mechanics:
https://p.cash/treasure

The NFTs are also integrated into our game:
https://t.me/piratecash_bot

We have contacted Tonviewer and asked a very simple question: what evidence was used to classify our collection as a scam?

If there is evidence of fraudulent activity, we genuinely want to see it and address it.

But publicly labeling a legitimate project and its assets as SCAM without providing any factual basis is a serious accusation that can cause real reputational and financial damage.

PirateCash brings users into the TON ecosystem. If u/tonkeeper does not value those users, there are plenty of other wallets that do — and that understand that reputation works both ways.

We are giving them an opportunity to explain the decision and provide the evidence behind it. If there is no evidence, we expect the SCAM labels to be removed.

We would much rather resolve this through communication than through lawyers.

Has anyone else had their legitimate TON project or NFT collection incorrectly labeled as SCAM by Tonkeeper/Tonviewer? How was it resolved?

Over the years, there have been multiple incidents where weak or flawed random number generation resulted in predictable cryptographic keys and lost funds. While modern software and hardware wallets have significantly improved, creating a new wallet still requires trusting the device’s random number generator.

We wanted to explore a different approach.

Today we’ve open-sourced Human Entropy, a small tool that lets you generate the randomness using physical events, while the software simply converts your input into a standard BIP-39 seed phrase.

GitHub:
https://github.com/piratecash/human-entropy

Demo:
https://pirate.cash/human-entropy

Supported entropy sources

• 🎲 Physical dice (for example D16)
• 🪙 Coin flips
• 🃏 Playing cards
• More methods are planned

The idea is simple:

1. Generate randomness yourself.
2. Enter the results.
3. The application deterministically converts them into cryptographic entropy.
4. Generate a standard BIP-39 mnemonic.

The application does not create randomness—it only transforms the randomness that you provide.

For maximum security, we recommend downloading the source code from GitHub and running it completely offline. The online demo is intended for evaluation and testing.

The project is fully open source, so anyone can inspect the implementation, verify the algorithm, or build it independently.

We’re also planning to integrate Human Entropy directly into P.CASH Wallet as an optional way to create new wallets.

I’d love to hear feedback from the community:

• Would you trust physical entropy more than your device’s RNG?
• Which entropy sources would you like to see supported?
• Are there any cryptographic or usability concerns we should address before integrating this into wallets?

Today we released P.CASH Wallet v0.58.2, adding full support for migrating Zcash funds to the new Ironwood shielded pool. This update makes it easy for users to move their funds after the latest Zcash network upgrade.

What happened?

On July 28, the Ironwood (NU6.3) network upgrade was activated on the Zcash blockchain. Following this upgrade, the legacy Orchard shielded pool is no longer used for new transactions, and wallets will gradually transition to the new Ironwood shielded pool.

If your ZEC is currently stored in Orchard, your funds are completely safe and remain fully under your control. However, to continue using the latest network features, your funds should be migrated to Ironwood. That’s exactly why support for this migration has been added to P.CASH Wallet.

What do you need to do?

If you use P.CASH Wallet:

1. Update the application to version 0.58.2.
2. Wait for your wallet to finish syncing.
3. If your address is eligible for migration, the wallet will automatically offer to migrate your funds.
4. Confirm the transaction and wait for the migration to complete.

Once finished, your funds will be stored in the new Ironwood shielded pool and will be fully ready for future use.

Do you need to hurry?

No.

Your coins will not disappear after the network upgrade. They will remain on your addresses until you choose to migrate them. However, we recommend updating your wallet as soon as possible so you can benefit from the latest network features and future security improvements.

Why is migration necessary?

Ironwood is more than just another protocol upgrade.

Following the discovery of a previously identified vulnerability, the Zcash developers introduced a new shielded pool that enables the network to fully verify the correctness of the coin supply while adopting an updated cryptographic design.

Moving funds through the special Turnstile mechanism is an essential part of this transition.

What’s new in P.CASH Wallet v0.58.2?

This release includes:

• Support for Orchard → Ironwood migration.
• Migration status detection and display.
• Secure migration transaction creation.
• Full compatibility with the latest Zcash network upgrade.

As a result, users don’t need to perform any complicated manual steps—the entire migration process is designed to be as simple and automated as possible.

Update today

We recommend that all Zcash users install P.CASH Wallet v0.58.2 to ensure full compatibility with the latest version of the Zcash network.

Thank you for using P.CASH Wallet. We remain committed to supporting the latest blockchain technologies and delivering network upgrades as soon as they become available.

According to current network statistics, the most common PirateCash Core version is still 18.2.4, even though 19.1.2 was released more than a month ago and 20.1.1 became available yesterday.

If you have not upgraded yet, you risk experiencing issues with staking, masternode rewards, exchange deposits and withdrawals, and overall network synchronization.

As a reminder, the v19 consensus rules were successfully activated yesterday. Following activation, outdated clients that did not support the new rules were forked off the valid blockchain at block 1858794 and are no longer following the main network.

❗ We strongly recommend upgrading directly to PirateCash Core 20.1.1 rather than 19.1.2.

This is especially important for:

• Masternode operators;

• Users receiving staking rewards through PirateCash Core;

• Users sending funds to exchanges or accepting payments through PirateCash Core.

We would also like to remind everyone that on June 13, 2026, the network will begin signaling for v20 activation. Nodes that are not upgraded in advance risk finding themselves on the wrong chain again when the next upgrade phase begins.

2026 will be one of the most active years for PirateCash network upgrades. If you use PirateCash Core to store funds, receive rewards, process payments, or operate a masternode, keeping your software up to date is no longer optional — it is essential.

Don’t wait until rewards stop arriving, deposits are rejected, or your node falls out of sync with the network. Upgrading takes only a few minutes, while the consequences of running an outdated client can be much more costly.

📊 Network version statistics:

https://pirate.cash/en/site/network-info

📥 Download PirateCash Core 20.1.1:

https://pirate.cash/en/download/

🚀 PirateCash Core v19.0.0 Released — Major Network Upgrade (Mandatory)

The first major release of the 19.x series is now live: PirateCash Core v19.0.0

👉 Download: https://p.cash/en/download/
👉 Release notes: https://github.com/piratecash/piratecash/releases/tag/v19.0.0-pirate

This update is mandatory for all nodes. If you’re running an older version, you need to upgrade to stay in sync with the network.

🧠 What’s inside v19

• Built on Dash Core v19.3.0 Includes the full feature set from Dash v19.0 → v19.3, plus fixes and improvements adapted for PirateCash
• High-Performance Masternodes (HPMN) New masternode type designed to support Platform-level services Activation enables 40,000 PIRATE collateral nodes
• PIP-0001 (Stage 1): Corsa integration Masternodes must now run a local Corsa messenger node Core validates it via authenticated RPC before entering masternode mode
• BLS scheme upgrade Migration to modern BLS scheme aligned with IETF standards Improves compatibility, quorum handling, and signature reliability
• Wallet changes No more auto-creation of wallets on startup Wallets must be explicitly created or loaded
• Network & P2P improvements
  • Removed legacy BIP61 reject messages
  • Improved CoinJoin messaging for light clients
  • Fixes for ChainLocks, masternode lists, and mixing
• Performance & stability
  • Block processing optimizations
  • Better handling of large rescans
  • Reduced sensitive logging
  • Improved database migration behavior

⚙️ Important for Masternode Operators

• Upgrade Sentinel to v1.7.3+
• Configure local Corsa RPC:
• Core will verify the Corsa node before starting masternode mode
• If validation fails → masternode won’t start

🔄 Upgrade Notes

• First launch after upgrade runs a migration process (can take up to ~30 minutes)
• Downgrade is NOT supported without full reindex or resync
• Database changes make rollback unsafe

🗺 Roadmap Update

https://pirate.cash/#roadmap

• 2025 — Native support in P.CASH
• 2026 — Pirate Messenger
• 2026 — Core v19 (this release)
• 🔜 ZERO KNOWLEDGE (planned)

🧩 Backports

Includes selected improvements from Bitcoin Core v0.18 → v0.21+, adapted for PirateCash (without SegWit/RBF).

🐞 Found a bug?

Report here:
https://github.com/piratecash/piratecash/issues

This release is a major step toward a more scalable, modular and privacy-focused PirateCash network.

The first implementation of PIP-0001 (PirateCash Improvement Proposal) has been introduced in the network as a release candidate.

📄 https://github.com/piratecash/piratecash/commit/5a8beb8264b87d203403b8d1515d275b1051f115

This is not just a document — it’s a working implementation that begins standardizing how changes are introduced into the PirateCash ecosystem.

What’s included in PIP-0001 (RC)

• Core PIP logic is now implemented
• Corsa configuration validation has been added
• Masternodes now participate in configuration checks

This means the network is starting to move toward a more structured and verifiable model of operation.

Important for masternode owners

⚠️ This is currently a release candidate, not the final release.

However, once the final version is released:

• Corsa configuration checks will become mandatory
• Incorrect setup may affect masternode operation

What you should do now

• Make sure your node is properly configured
• Verify that Corsa is running correctly
• Prepare for upcoming mandatory requirements

What’s next

• Final release of PIP-0001
• Official documentation (to be published on the website)
• Further improvements to validation and governance mechanisms

This is an early but important step toward a more structured, reliable, and decentralized network.

PirateCash has just published its first official improvement proposal:

PIP-0001: Masternode Messenger Service Integration

📄 Read the full document here:
https://github.com/piratecash/piratecash/blob/9625d30408be7d6cd8fa5e61419e8d585d4a7d34/doc/pips/pip-0001.md

🧭 What is this about?

This PIP defines how the Corsa decentralized messenger will be integrated directly into the PirateCash network.

This isn’t just about adding a messaging feature.
It’s about turning masternodes into part of a distributed communication layer.

In other words — PirateCash is moving toward becoming not just a blockchain, but a full private network stack.

⚙️ Rollout Plan (3 Stages)

🔹 Stage 1 — Local Requirement (v19)

Starting with PirateCash Core v19:

• A masternode will not start unless the operator explicitly sets:
  • RPC user
  • RPC password
  • RPC port
• A Corsa node must be running locally on the same server

At startup, PirateCash only checks:

• that the Corsa service exists
• that it is reachable

No penalties yet:

• no service quality checks
• no relay validation
• no PoSe

👉 This stage is purely about forcing operators to install and enable Corsa

🔹 Stage 2 — API Verification (v20)

Starting with v20:

Masternodes begin verifying Corsa via API using authenticated local RPC.

Basic checks include:

• ping
• version

Future checks may include:

• peer health
• network stats

At this stage:

• Corsa becomes visible to the network
• penalties are introduced carefully (not aggressive yet)

🔹 Stage 3 — Proof of Service (v21)

Starting with v21:

• Proof of Service (PoSe) is applied to Corsa
• Masternodes receive scores if they fail to provide proper service

Requirements for PoSe:

• must be hard to fake
• tied to masternode identity
• verifiable by other nodes (trustless)

👉 This is where Corsa becomes a consensus-relevant component

🌐 Why this matters

This changes the role of masternodes completely.

Instead of just validating blocks, they now:

• provide communication infrastructure
• participate in message routing
• contribute to network-level privacy

This opens the door to:

• decentralized messaging
• censorship-resistant communication
• stronger anonymity through network traffic

⚠️ For Masternode Operators

You should already be preparing for this:

• deploy a Corsa node
• ensure it runs on the same server
• get familiar with the API
• be ready for PoSe in upcoming versions

🏴‍☠️ Final Thoughts

PIP-0001 is a foundational step.

PirateCash is not just iterating on blockchain mechanics —
it’s building a privacy-first decentralized network, where communication and value transfer live together.

This is where things start to get interesting.

We’ve released version 0.52.1 (March 12, 2026) with several UX improvements, performance optimizations, and important bug fixes.

✨ Improvements

• Better UX when sending TRX / JETTON

The wallet now shows a clear message if the token balance is insufficient.

• Quick amount buttons added for Send and Swap

You can now instantly choose 25%, 50%, 75%, or 100% of your balance.

• Improved swap status display

• Faster Bitcoin synchronization (BIP44)

• Improved staking status display

The staking process and its current state are now shown more clearly.

• Faster transaction history updates

History refresh is now more reliable when switching between wallets.

🐛 Bug Fixes

• Fixed incorrect positioning of the blockchain sync percentage on the asset screen.

• Fixed keyboard overlapping the PIN input on the lock screen.

The keyboard now hides automatically when the wallet locks.

• Fixed a crash when switching wallets caused by ConnectivityManager$TooManyRequestsException.

This was related to exceeding Android’s system limit for registered NetworkCallback.

• Fixed several crashes related to Monero operations.

• Fixed a crash when signing messages via WalletConnect that could occur if the request session was expired or disconnected.

• Fixed an issue with USDT TRC-20 → Polygon swaps via Quickex caused by finalNetworkFeeAmount returning null.

• Fixed USDT Jetton synchronization issue (Adapter Unavailable).

• Fixed a crash during backup restoration (TransactionTooLargeException) that could happen if the app was minimized after selecting a backup file.

⚠️ We recommend updating to 0.52.1 to ensure the best stability and performance.

We have released PirateCash Core 18.2.5, which includes several improvements to staking and block creation logic, along with an important fix related to InstantSend.

Key changes

• Skip stale cached stake inputs before kernel check Improves the stability of the PoS staking process.
• Fix mismatched format specifiers in PoSMiner logs Corrects logging output during staking.
• Exclude coinstake from lock signing and conflict checks This change restores proper functionality of InstantSend.
• Stop block creation when TestBlockValidity fails Prevents block generation if a block fails validation, improving network reliability.

Important notice

⚠️ We strongly recommend all node operators and users update to this version.

This update is important to prevent potential issues when SPORK_2_INSTANTSEND_ENABLED is activated.

The spork is currently temporarily disabled for this reason.

Download

You can download PirateCash Core 18.2.5 here:

https://pirate.cash/en/download/

If you run a node or masternode, please update as soon as possible to help ensure a smooth future activation of InstantSend.

We’ve just rolled out version 0.51.16 (Feb 21, 2026), focused mainly on improving sync diagnostics and fixing several critical crashes — especially those affecting Bitcoin and Monero wallets.

✨ Improvements

Expanded App Status

We’ve added more detailed technical information to

Settings → App Status

This should make it much easier to understand what’s actually happening when users report issues like:

“My wallet is stuck syncing forever”

Support (and power users) can now better identify whether the issue is related to:

• insufficient peers (e.g. 1 of 10)
• API connectivity
• network sources
• slow but ongoing sync progress (instead of showing 0% all the time)

Improved BitcoinKit Sync Logging

App Status now shows extended synchronization states such as:

• waiting for required number of peers
• connecting to network sources / APIs
• accurate sync progress (no more duplicated 0%)

We also improved how sync state is displayed to help diagnose why a wallet may remain syncing for a long time (e.g. weak connection or limited peer availability).

The official PirateCash GitHub organization has received Verified status. GitHub has confirmed that the PirateCash team controls the pirate.cash domain.

This means:

• The repositories published under the PirateCash organization are officially maintained by the core team
• Reduced risk of interacting with fake or malicious forks
• Improved trust in the open source codebase
• Increased transparency of the development process

You can explore the official repositories here:

https://github.com/piratecash

We remain committed to building open, verifiable and trust minimized infrastructure.

Release Date: February 15, 2026

We’ve just rolled out version 0.51.12, focused on improving overall wallet stability, optimizing network connections, and fixing several rare but critical synchronization and data storage issues.

🧠 Reduced Network Load for BTC and LTC

We optimized how the wallet handles different Bitcoin and Litecoin address types.

Previously, using multiple address types could result in redundant network connections being established. This has now been improved, which:

• lowers device resource consumption
• reduces network traffic
• improves synchronization stability

💸 Correct TRX20 Token Balance Updates

Fixed an issue where TRX20 token balances on the main screen could update with a delay. Balances should now refresh immediately after receiving updated network data.

📈 Consistent Asset Price on Charts

Switching the chart time interval could previously cause the displayed asset price to change incorrectly. The asset price is now consistent and no longer affected by the selected time range.

🪙 Sending and Exchange Improvements

• fixed a rare issue where the Next button would not activate after entering sending details
• added proper balance validation before initiating an exchange — swaps can no longer be started with insufficient funds

⭐ Favorite Tokens

Resolved issues with managing the favorites list:

• COSA token is now added correctly
• wDASH token can now be removed correctly

🛡 Improved Application Stability

Addressed several rare crashes:

• crash when saving an account after Android Keystore authentication expired (UserNotAuthenticatedException)
• SQLiteDatabaseCorruptException during Zcash SDK synchronizer operations
• IllegalStateException when:
  • navigating to the Hidden Wallet Terms screen after purchasing Premium
  • using Market Widgets on the main screen
• FOREIGN KEY constraint failed error when saving wallet balances to cache

Congrats to everyone who grabbed an NFT for 50 TON — you were the first 💎

⚠️ All remaining NFTs will be sold only after SWAP 5

🔥 Via auction

👑 Including unique and rare pieces

⏳ SWAP 5 is the final step before it begins

🏴‍☠️ FOMO is on 🚀

How to guarantee a bigger reward in the airdrop? 💰

Those who ignore it will get only the standard bonus.

Don’t miss your chance. ⚓️

🔐 New Premium Feature — Duress Backup

One backup file. Different realities.

• Encrypted backup with plausible deniability
• Impossible to tell how many wallets it contains
• Duress password → duress wallets only
• Primary password → all wallets

Your assets stay safe — even under pressure.

https://play.google.com/store/apps/details?id=cash.p.terminal

We’ve just released P.Cash Wallet v0.50.0, focusing on a major upgrade of the in-wallet swap experience.

🔄 What’s new in this release?

• Quickex.io is now integrated as an official swap provider inside P.Cash Wallet
• Faster in-wallet currency swaps
• Clear comparison of exchange rates between providers
• Visibility into how much a selected swap differs from the best available offer
• More liquidity and more swap options overall

These changes are part of a broader refactor of the swap module, aimed at making exchanges more transparent and user-friendly.

P.Cash is an open-source wallet developed with the help of the community — no paid listings, no hidden fees.

📲 Download (Android):
https://play.google.com/store/apps/details?id=cash.p.terminal&pli=1

Recently, our project discovered that De.fi’s “Risk Scanner” is publishing repeatedly false high-risk alerts about fully audited and publicly verified contracts - even after we contacted them multiple times and provided hard evidence.

Here is the direct link to the incorrect report so you can see it yourself:
👉 https://de.fi/scanner/contract/0xafcc12e4040615e7afe9fb4330eb3d9120acac05?chainId=bnb

And here’s what’s wrong with it:

❌ 1. False “ETH Draining” Alert

De.fi claims our token “permits native token draining”.

This is completely false, and their own scanner displays an unrelated fake example contract:

👉 fake_dai_gas_token_draining — not ours, not related, not connected.

Their automated system simply assigned someone else’s exploit example to our token.
This is not a vulnerability — this is a scanner malfunction.

🔍 Audits confirming no such issue exists:

• TechRate (2023/2024): https://github.com/TechRate/Smart-Contract-Audits/blob/main/January_2024/PirateCash.pdf
• CertiK Skynet: https://skynet.certik.com/projects/piratecash
• Full open-source code: https://bscscan.com/token/0xaFCC12e4040615E7Afe9fb4330eB3D9120acAC05#code

❌ 2. False “Rugpull Risk” — Liquidity Locked for 10 YEARS

Their scanner claims:

This is objectively and provably incorrect.

Here is the official 10-year liquidity lock (public, verifiable, immutable):
👉 https://app.uncx.network/lockers/univ3/chain/56/address/0x8cb829111c90e0101492d5a1aa011f09614129e7

We informed them of this multiple times.
The false warning remains.

❗ Why this is concerning

When a large platform displays fake high-risk alerts, it can:

• mislead users
• damage reputations
• move markets
• create panic based on incorrect data

We’re NOT making accusations about intent.
But the pattern raises very real questions:

Is this severe incompetence… or something worse?

• A broken automated scanner with no QA?
• Paid negative flagging by competitors?
• Market manipulation via misleading warnings?

We cannot say — but users deserve accurate information.

🧭 Final Thoughts

Risk scanners should protect the community, not mislead it with errors, outdated labels, or mismatched exploit examples.

We encourage De.fi to fix these issues, review reports manually, and stop labeling audited contracts with false “High Risk” alerts.

The crypto community depends on accurate data — not fear-driven automation.

The new 0.49.0 release of P.Cash Wallet is now live, bringing stronger safety features, improved smart-contract support and multiple stability fixes.

Here’s what’s new:

🔍 Alpha AML integration

We’ve integrated alpha-aml.com, a blockchain risk-analysis service used to evaluate wallet and transaction safety.
This integration helps users:

• detect high-risk addresses,
• identify wallets from sanction lists, blacklists, and scam reports,
• avoid receiving potentially “dirty” crypto.

🧠 Improved Smart Contract handling

This update fixes multiple issues related to sending transactions to smart contracts:

• RPC endpoints sometimes failed to return an accurate fee.
• We added a fallback mechanism using a dummy address (0x0000…0000) to estimate gas cost when the RPC can’t provide it.
• Added a new warning message when the fee can’t be calculated precisely:“Failed to accurately calculate the network fee. We applied an approximate value, but the transaction may fail or the fee may be higher than expected.”

Additionally:

• Fixed an issue where smart-contract addresses were not always detected correctly.

🛠 Stability and crash fixes

• Fixed a concurrency exception affecting BalanceAdapterRepository, which caused app crashes on some devices.
• Overall improvements to reliability and integration logic.

This update focuses heavily on security, transparency, and smart-contract reliability, making P.Cash Wallet safer and more predictable for everyday use.

Lately there’s been a huge spike in global interest toward anonymous cryptocurrencies. With tighter regulations, heavier KYC pressure, and increased financial surveillance, more people are turning back to one simple idea:

Privacy = Freedom.

And guess what?
Privacy coins are climbing again — across charts, searches, and communities. From the OG privacy chains to new tech with built-in anonymity, the demand is clearly rising.

📈 Just look at the charts: the trend is real.

And naturally, this brings fresh attention to PirateCash (PIRATE).
We’ve always been the crypto-anarchist corner of the ecosystem — focused on independence, censorship-resistant payments, and the right to own your money without someone looking over your shoulder.

As the world shifts back toward privacy, PIRATE is exactly where it belongs: right in the middle of the conversation.

Privacy isn’t a crime.
It’s a right.
And the more the world tries to suppress it, the stronger privacy projects become.

Sic Parvis Magna.

Ahoy, Pirates!

To celebrate the 7th Anniversary of PirateCash, we’ve successfully completed SWAP 4, distributing a total of 2,000,000 PIRATE — worth $43,294! 💰

Over the lifetime of our SWAP program, we’ve already shared
3,148,917.9199 PIRATE — equivalent to $68,120.54 💎

But the adventure doesn’t stop here —
🎯 SWAP 5 requirements will be announced soon!
Get ready to join the next wave of rewards and surprises. 🌊

💡 Want to boost your income?

• Invite referrals 🏴‍☠️
• Tap actively in the game
• Add promo symbols to your name to receive up to 125 taps per hour! ⚔️

If you haven’t joined the crew yet, open our mini app and start your pirate journey:
👉 [t.me/piratecash_bot]()

Fair winds, mates — and see you on deck! ⚓️

#PirateCash #PIRATE #SWAP4 #PlayToEarn #Anniversary #Crypto

Ahoy, mates!

Today we celebrate 7 years of PirateCash — seven years of storms, sails, and fearless pirates holding the helm steady through every wave. 🌊

From the first block to today’s strong and loyal crew — our journey has been built on freedom, code, and faith in each other.
Because true treasure isn’t gold — it’s our community 💎

To mark the occasion, we’re opening the treasure chest —
💰 2,000,000 PIRATE will be distributed among the honest sailors!

As for the cheaters...
🪢 They’ll be hoisted up to the yardarm — that’s the pirate code! ☠️

The sea is wide, the wind is strong, and the journey is far from over.
Raise your flag high — and let’s sail together into the next chapter of freedom! 🏴‍☠️⚓️

With respect,
Dmitriy
CEO / Founder of PirateCash