@TheDealMakerGuy Not good news. Gives the state constant total oversight of every business transaction โ classic surveillance state stuff, unfit for a free society. Plus, any breach hands competitors your full client/sales data.
@TheDealMakerGuy People in Poland don't seem to understand that KSeF isn't a Polish initiative, it's a EU directive, discussed for years and formally voted by the EU parliament last year. All countries are mandated to implement it, all are working on it atm. See https://t.co/7k60LuXGsZ
@r0bre In good part because being explicit forces to understand the execution and the logical flow. So if you write native solana (pinocchio or solana_program) and you systematically check your accounts (e.g. check signer, deriving PDAs), I'd argue that you're just as safe, if not more
@r0bre matches my experience in backend code. Devs using big, bulky frameworks (with background operations in macros or methods that they don't see and know) are often way worst than devs writing simpler, cleaner functions where the execution is transparent and explicit.
@PaulRBerg - Same language as the smart-contract. Can be a con if you plan to build your txs from another language. For example, if you rely on a TS SDK to tell which tick account you should use when building your DEX swap txs, then maybe better to write tests in TS
@PaulRBerg - Feature rich. E.g. allows to alter sysvars (clock, ...), includes sig verifications, etc. Unlike ix-based test lib like Mollusk.
- Faster than JS/TS libs
- More stable and LT support than say bankrun or litesvm. Because maintained by Anza and used in SPL programs
2000+ $SOL IN LIQUIDITY SEEDED ๐ง๐ง๐ง
1000+ $SOL IN ENTROPY BURNED ๐ฅ๐ฅ๐ฅ
WE GOT BIG BALLS 'CAUSE ๐๐๐
SOMEONE HAS TO HAVE 'EM ๐๐๐
#EEEE $ENT #PureDePIN