Guy

[Guy @remember_511]

$ZKAS is at a turning point for better or worse. Choose wisely, but take a step back and look at the bigger picture. Be wary of anyone with too much ambition to run a project which isn’t theirs. What the developer does here should speak volumes. I’m watching.

[Guy @remember_511]

@ZethoraNetwork @Klein0gn @CEOGHOXST With such a steep learning curve with Rust EVM, what are the real chances of on-boarding anyone at all to carry the dev torch? I think if you go, no one is likely to continue the work. I hope I’m wrong but this is much too centralized right now to succeed.

[Guy @remember_511]

@ZethoraNetwork @Klein0gn @CEOGHOXST Who is “we”?

[Guy @remember_511]

@ZethoraNetwork @ZKas_X Also, can you address concerns of centralization? As you are the sole developer, how can your project remain safe and impartial? What happens if you die? Does the project die as well? Is there public access to the repo?

[Guy @remember_511]

@ZethoraNetwork @ZKas_X Ok so, try again. Also, your ledgers are exposed with optional privacy. Ask @Zcash . Tell me again, what’s the difference other than an optional privacy feature? Maybe @ZKas_X can give an objective answer?

[Guy @remember_511]

@ZKas_X @Poloniex @poloniex can figure out Kaspa but not ZKAS? Weird.

[Guy @remember_511]

5th of November. #NeverForget

[Guy @remember_511]

@Adebayo_Faboro Who’s to say a rogue AI program didn’t perform the hack is what I mean.

[Guy @remember_511]

@CaffeSatoshi Send ETH to Dex. ETH—->XMR

[Guy @remember_511]

A byproduct of merge mining written into $ZKAS code? It’s perfectly eco-friendly. Kaspa miners need not use a single extra watt of electricity to mine it!

[Guy @remember_511]

Truly, the developers of $ZKAS have solved a decade-old problem:
Achieving mandatory, on-chain privacy without sacrificing lightning-fast scalability.
This is ground breaking and extremely unique. Transactions sent with the stealth & speed of a ninja’s dagger.
⚡️ 🥷⚡️

[Guy @remember_511]

The $ZKAS team managed to marry heavy privacy math with rapid throughput. This is a notoriously difficult bit of blockchain engineering only made possible with BlockDAG tech. kHeavyHash mining + GHOSTDAG consensus + Orchard/Halo2 privacy has created an absolute monster.

[Guy @remember_511]

So very interesting this fork of $KAS, $ZKAS . The coding isn’t just copy paste. They’ve actually torn it open to stitch in $ZEC privacy architecture. They modified its state transitions to mandate private-by-default transactions. No one does this easily. They’re the real deal.