FAQ

Frequently Asked Questions

Explore the most commonly asked questions and get your answers right away.

Pirate Chain is a project about financial freedom. It provides 100% shielded z-z P2P transactions to preserve the privacy and anonymity of the user. It is run by a passionate community of volunteers.

Whilst Proof of Work is a great consensus mechanism to verify transactions, blockchains that only utilize PoW with small levels of hashing security can be attacked as the market value of those blockchains increases over time with what is known as a 51% attack (double-spending attack).

 

Delayed Proof of Work notarizes the transactions made on Pirate on to the Komodo blockchain, and then on to the Bitcoin blockchain. This was added to make Pirate more secure than any other Proof of Work chain out there by being resistant to 51% attacks. This is what makes it special compared to others.

Pirate OS is our series of operating systems that we are developing to enhance the security and privacy of those making transactions. Think of it as an environment to run your wallet with the peace of mind of all the security features in place without the exploits and bugs the other operating systems have, plus its transportable since it is burned onto a USB. You simply power down your PC, plug in the usb, then boot from the usb itself and the operating system comes up. This has the distinct advantage of having the ability to transport your wallet anywhere with the USB, while being able to use it on almost any computer. The OS has MAC address spoofing, runs over TOR, and will eventually have the data encrypted as well as run over several VPNs. This ensures that your wallet is safe, secure and virtually untraceable when you make transactions.

The reason why this is true is that ZCash does not shield all of their P2P transactions, which ruins fungibility and their privacy. Zcash utilizes transparent addresses and those transactions make up 98% of their chain. This is not private. Aside from initial block rewards to pools, all of our transactions are private. Also, we have a bigger anon set and use dPoW.

 

Monero offers a private chain, but their privacy tech is inferior to ZCash. Fluffypony himself stated that zk-SNARKs offers better privacy than Monero. So a fully shielded chain like ours offers better privacy, a bigger anon set and we are 51% attack resistant with dPoW.

We already solved the fungibility problem by shielding all of our P2P transactions.

Bitcoin is traceable. You can see exactly where everything goes, giving addresses linkability. If someone sends you bitcoin that came from a nefarious source, and the authorities know about it, you can be linked to that transaction. With Pirate, this cannot happen.

Pirate runs a couple Komodo Notary Nodes that donate funds to us every month, as well as having our main pools donate a portion of the pool fees to us. We profit by having these funds used toward development, community bounties, etc. We also raise funds from the community to help pay for things like exchange listings and more.

Specialized hardware is extremely efficient, and boast far more hash power, and thus security, per unit of electricity. They’re more reliable than home-built GPU miners, and allow miners to specialize, professionalize, and scale up. Additionally, ASICs are algorithm-specific, and could align miner incentives better with a specific project compared to GPUs, which are much more flexible. In a political vacuum, an ASIC-mined network is more efficient at processing blocks, plain and simple, and arguably more expensive to attack.

 

We decided just to embrace the ASICs, since they're here to stay and aren't going anywhere. On top of that, going through hard forks every few months just to combat them seems pointless and messy. So no, Pirate is not ASIC resistant.

With the sapling ceremony, there is really no issue with the trusted setup.

Read more on "Powers of Tau Ceremony" here:

- https://www.zfnd.org/blog/conclusion-of-powers-of-tau/
- https://www.coindesk.com/zcash-team-completes-powers-of-tau-ceremony-for-upcoming-hard-fork

Our main dev is MrLynch, who is absolutely brilliant, our core dev is jl777 who is also the lead developer of Komodo, radix42 who was one of the early BTC devs and she was also a Zcash dev, but is now a Pirate dev. ComputerGenie is one of our wallet devs, Wieprz is our PirateOS dev, and we have more devs that contribute from the Komodo ecosystem. We are always looking for more devs to fully round out our team though.

There is little to no compromise on anonymity. There is a small amount of metadata leakage to the insight server. The insight server will know the IP address associated with wallet transactions, based on the witnesses requested by the wallet. However, using a VPN would protect the user against that leakage.

Newly mined coins (coinbase transactions) go to a transparent address for supply auditability reasons.

 

"Even if 1 septillion ARRR existed, "the answer is that a cryptographic hash is used to publish a commitment to each created note, and the zero-knowledge proof ensures that for each JoinSplit transfer, the total amount specified in these commitments..."(plus the transparent output) matches the total amount spent from the inputs. The enforcement that the plaintext of notes is correct is done only when they are decrypted. In short, even if you make them in "secret" you cannot spend them because the numbers don't match and no one will accept the transaction." - ComputerGenie

 

"Pirate supply integrity is based on the coinbases mined and then reliance on sapling z -> z transactions not allowing to double spend or create new coins" - jl777

The main use case for Pirate is complete financial privacy. Nobody has a right to view your daily purchases, what you decide to buy, etc. Informational security and privacy is more important than most people realize. The benefit for holders is the knowledge of having their financial privacy secure and the ability to use Pirate in online shops (and eventually in person when we develop the Point of Sale system)

No.

 

The following link https://dexstats.info/richlist.php?asset=PIRATE only shows the unshielded mining rewards (which can still be shielded) and notarizations. Remember, there are only two exceptions for transparent transactions, which are the block rewards from mining and notarizations. All the other transactions are z2z.

"atomicDEX-API is a cross protocol. core layer
atomicDEX app is an app on top of the protocol core layer
komodod. is a cryptocoin daemon that PIRATE is based on

atomicDEX is. a totally separate thing than komodod daemon.

think about it this way. if some ETC (fork of ETH) dapp project adds KYC to their dapp, does. that affect the ETC daemon? does it affect the ETH daemon? PIRATE is independent chain in the komodo ecosystem. independence means it can. independently decide to do. things" - jl777

Scroll to Top