English
Max Soul 🧱
Report

Max Soul 🧱

@0xMaxSoul

Building @arcane_finance. Privacy-preserving compliance infrastructure for crypto. Making digital assets usable at institutional scale.

  • Joined
657 Following279 Followers553 Posts
  1. Max Soul 🧱@0xMaxSoul
    People often say that fundraising skills don’t align with being a good CEO. It's a misconception. The key to fundraising boils down to one skill: communication.
    21282.1K
  3. Max Soul 🧱@0xMaxSoul
    A real honor to take the stage at Meridian. Huge thanks to the Arcane team, @0xPredicate and @StellarOrg for making this happen. I got to hold the mic. A lot of people did the work.
    Stellar | Meridian Oct 28-29 @StellarOrg
    The Enterprise Privacy Stack is coming to Stellar. At #Meridian2026, @arcane_finance and @0xPredicate announced an infrastructure solution that combines transaction screening, confidential payments, and controlled access to data for investigations.
    00576
  5. Max Soul 🧱@0xMaxSoul
    Max Soul 🧱
    RT @arcane_finance: Institutions shouldn’t have to choose between confidentiality and compliance. Together with @0xPredicate, we’re bringing both sides into one stack: confidential transactions, built-in screening, and disclosure governed by your own policies. Built for financial products where privacy and accountability belong in the same workflow, on @StellarOrg.
    Stellar | Meridian Oct 28-29 @StellarOrg
    The Enterprise Privacy Stack is coming to Stellar. At #Meridian2026, @arcane_finance and @0xPredicate announced an infrastructure solution that combines transaction screening, confidential payments, and controlled access to data for investigations.
    0501
  6. Max Soul 🧱@0xMaxSoul
    Max Soul 🧱
    RT @arcane_finance: Arcane team will be at @StellarOrg Meridian in Lisbon, Oct 28 to 29. We'd love to meet teams exploring privacy for their products, from private payments to confidential assets. Let's discuss what you're building and how privacy and compliance can fit into it. If you'll be there, send us a message. Let's find a time to meet! #Meridian2026
    0101.3K
  7. Max Soul 🧱@0xMaxSoul
    So based. We're pushing similar rules internally
    immad @immad
    ✍️ Writing is essential to how @Mercury communicates as a 1300 person remote-first company. I wrote on Writing At Mercury (inspired by @vxanand's post). Principles of Writing at Mercury 1. Writing is thinking: Spending time on writing is not wasting time, it helps you process ideas, analyze problems, and explore solutions. 2. Less writing is better: Good writing is concise, which makes it easier to understand. 3. Reading should be easy: If >2 people will read your writing you should spend extra time making your writing good + digestible + clear etc. It is not fair for people reading to do work that the writer could have done for them. 4. Writing is expression: Your writing will be taken as an expression of your identity, so give it the care it deserves and be authentic. 5. Writing is important: Writing is the main way we communicate internally at Mercury, as a remote-first firm. We frame important discussions, and document thought processes and ultimate decisions, with our writing. On Using AI for Writing It is very easy to use AI to write a lot of content. If you do so, then by default you have: 1. Outsourced your thinking 2. Created a verbose/long doc 3. Made it hard to read 4. Have a doc that is not expressive and very bland 5. Watered down our discussions and decision making In other words, heavy AI use for writing is diametrically opposed to the principles of writing laid out above. Some effective ways that AI could be used instead: 1. Critiquing your writing 2. Condensing your writing 3. Shaping initial drafts 4. Summarizing complex information On Using AI to Respond on Slack/Comments Slack threads and comments are a particularly bad use of AI writing. 1. Slack responses and doc comments should always be short. Large blocks of AI text don’t belong. 2. AI used here is often thoughtless and the other party could have just used the AI tool themself. It inherently shows a disrespect for the reader’s time. 3. Given our remote culture, one of the main ways we connect with each other is via Slack. Using AI often would obscure your authentic perspective. 4. It would be better to share the prompt you gave to the AI directly to the other person and they can just prompt their own AI tool. How to do Great Writing at Mercury We aren’t going to police whether someone is using AI or not to help them write. We will just have a high standard for your writing output. Here are some high-level rules that should help: 1. Always read and stand by 100% of your written output. 2. When it is important, spend time on your writing. You might spend time on the narrative arc, the tone, the structure, whether it clearly articulates an issue, explores solutions, and drives toward an outcome. 3. Think hard about how you can use fewer words and be more concise. 4. Be authentic. You don’t need to dress up your writing in corporate jargon to make it sound professional. Simple, plain writing is often more effective. 5. Never copy-paste AI responses to someone in Slack or to comment on a doc. 6. Sometimes it's better to write nothing at all. Don’t make a comment in a doc/slack because you want to be part of the convo, say it if it materially moves things forward.
    013137
  8. immad✓@immad
    ✍️ Writing is essential to how @Mercury communicates as a 1300 person remote-first company. I wrote on Writing At Mercury (inspired by @vxanand's post). Principles of Writing at Mercury 1. Writing is thinking: Spending time on writing is not wasting time, it helps you process ideas, analyze problems, and explore solutions. 2. Less writing is better: Good writing is concise, which makes it easier to understand. 3. Reading should be easy: If >2 people will read your writing you should spend extra time making your writing good + digestible + clear etc. It is not fair for people reading to do work that the writer could have done for them. 4. Writing is expression: Your writing will be taken as an expression of your identity, so give it the care it deserves and be authentic. 5. Writing is important: Writing is the main way we communicate internally at Mercury, as a remote-first firm. We frame important discussions, and document thought processes and ultimate decisions, with our writing. On Using AI for Writing It is very easy to use AI to write a lot of content. If you do so, then by default you have: 1. Outsourced your thinking 2. Created a verbose/long doc 3. Made it hard to read 4. Have a doc that is not expressive and very bland 5. Watered down our discussions and decision making In other words, heavy AI use for writing is diametrically opposed to the principles of writing laid out above. Some effective ways that AI could be used instead: 1. Critiquing your writing 2. Condensing your writing 3. Shaping initial drafts 4. Summarizing complex information On Using AI to Respond on Slack/Comments Slack threads and comments are a particularly bad use of AI writing. 1. Slack responses and doc comments should always be short. Large blocks of AI text don’t belong. 2. AI used here is often thoughtless and the other party could have just used the AI tool themself. It inherently shows a disrespect for the reader’s time. 3. Given our remote culture, one of the main ways we connect with each other is via Slack. Using AI often would obscure your authentic perspective. 4. It would be better to share the prompt you gave to the AI directly to the other person and they can just prompt their own AI tool. How to do Great Writing at Mercury We aren’t going to police whether someone is using AI or not to help them write. We will just have a high standard for your writing output. Here are some high-level rules that should help: 1. Always read and stand by 100% of your written output. 2. When it is important, spend time on your writing. You might spend time on the narrative arc, the tone, the structure, whether it clearly articulates an issue, explores solutions, and drives toward an outcome. 3. Think hard about how you can use fewer words and be more concise. 4. Be authentic. You don’t need to dress up your writing in corporate jargon to make it sound professional. Simple, plain writing is often more effective. 5. Never copy-paste AI responses to someone in Slack or to comment on a doc. 6. Sometimes it's better to write nothing at all. Don’t make a comment in a doc/slack because you want to be part of the convo, say it if it materially moves things forward.
    223452846.4K
  9. Max Soul 🧱@0xMaxSoul
    We want businesses onchain. Asking them to livestream their payroll to competitors is a strange way to get there. Talking this through with @AVotoFuture 👇
    Arcane @arcane_finance
    A conversation with @0xMaxSoul and @AVotoFuture from @StellarOrg on whether privacy remains a key blocker to institutional on-chain activity.
    014119
  12. Max Soul 🧱@0xMaxSoul
    Max Soul 🧱
    RT @0xPredicate: Once transactions are confidential and private, how do you screen users, respond when their risk changes, and produce evidence for a lawful investigation? In partnership with @arcane_finance, we built a unified onchain compliance stack for private financial applications on @StellarOrg for just that. The partnership utilizes our compliance workflows with @arcane_finance's confidential environments. Privacy shouldn’t come at the expense of compliance, and we're excited to build systems designed to operate for global scale
    Arcane @arcane_finance
    0802
  14. Max Soul 🧱@0xMaxSoul
    Max Soul 🧱
    RT @arcane_finance: Arcane Podcast episode #4 is live. In our latest podcast episode, @0xMaxSoul and Turpal Makh speak with @AVotoFuture from @StellarOrg about the role of privacy in institutional adoption of public blockchains. Topics include: → Institutional blockers for public blockchains → Confidential transactions → Counterparty privacy + privacy pools → Compliance-ready private transactions → AI-driven on-chain de-anonymization risks A conversation for teams exploring privacy, compliance, and institutional blockchain adoption. Watch the full episode ↓
    01003
  15. Max Soul 🧱@0xMaxSoul
    Consensus Miami has been a good reminder that the industry is growing up. The interesting conversations are less about “what’s the next meta?” and more about what actually needs to exist for crypto to scale: privacy, compliance, and real institutional usability. I’m around in Miami this week. If you’re here too, DM me. Would be great to catch up.
    Download
    1116444
  18. Max Soul 🧱@0xMaxSoul
    I’ll be at @EthereumDenver Mon-Fri. If you’re working on privacy, compliance or institutional crypto infrastructure, let’s connect.
    006134
  19. Max Soul 🧱@0xMaxSoul
    I think the underrated advice for those web3 devs who are seeking a job is to ... apply for it! Frankly I haven't seen in a while an HR browsing some repos to find a dude that can (vibe)code a random toy app. I guess Claude Code can spit out all of that in minutes now. It's so hard to distinguish noise from signal these days.
    Suraj Sharma @suraj_sharma14
    10 Blockchain Projects That Will Get You Hired in 2026: 1. Onchain Indexer + Query Layer (Production-grade) Build a scalable indexer for onchain data with real queries and caching. What it proves: > You understand onchain data ≠ RPC calls > You know infra pain points Stack : Ethereum / L2 + Subgraphs or custom indexer + PostgreSQL / ClickHouse + API layer 👉 2. Smart Contract Security Playground A repo that demonstrates common vulnerabilities with exploits and fixes. What it proves : > Security-first mindset > You understand failure modes Stack : Solidity + Foundry / Hardhat + Slither / Echidna 👉 3. Account Abstraction Wallet (Real UX) Build a minimal AA wallet with gas abstraction and recovery. What it proves : > You understand UX + protocol trade-offs > You’re future-facing Stack : ERC-4337 + Bundler + Paymaster + Frontend (React) 👉 4. DEX Analytics & MEV Visibility Tool Track swaps, slippage, MEV impact, and liquidity movement. What it proves : > Protocol-level understanding > Economic intuition Stack : Uniswap / DEX + Indexer + Data viz +Python / JS 👉 5. Cross-Chain Message Verifier Verify and visualize how cross-chain messages are validated and fail. What it proves : > You understand cross-chain risk > Architecture-level thinking Stack : Any cross-chain protocol + Event listeners + Fraud / verification logic 👉 6. Layer 2 Security Comparison Dashboard Compare trust assumptions of different L2s. What it proves : > You can reason about security models > You understand rollup designs Stack : Ethereum+ L2 docs + contracts + Visualization layer 👉 7. Onchain Governance Simulator Simulate DAO proposals, voting power shifts, and attack scenarios. What it proves : > Governance + incentive understanding > Systems thinking Stack : DAO frameworks + Token logic + Simulation scripts 👉 8. ZK Proof Demo with Real Use Case Not “hello world ZK” show proof verification in a real flow. What it proves : > You understand ZK beyond buzzwords > High-signal skill Stack : Circom / Noir + Verifier contracts + Frontend proof generation 👉 9. Formal Verification Case Study Formally verify one real-world contract and explain the results. What it proves : > Precision > Professional security mindset Stack : Certora / Scribble / Foundry + Write a human-readable report 👉 10. Blockchain Incident Post-Mortem Repository Analyze past hacks and explain why they happened. What it proves : > Deep learning from failure > Communication + technical clarity Stack : Real incidents + Diagrams + Clear write-ups 👉 (save it)
    004134
  20. Suraj Sharma✓@suraj_sharma14
    10 Blockchain Projects That Will Get You Hired in 2026: 1. Onchain Indexer + Query Layer (Production-grade) Build a scalable indexer for onchain data with real queries and caching. What it proves: > You understand onchain data ≠ RPC calls > You know infra pain points Stack : Ethereum / L2 + Subgraphs or custom indexer + PostgreSQL / ClickHouse + API layer 👉 2. Smart Contract Security Playground A repo that demonstrates common vulnerabilities with exploits and fixes. What it proves : > Security-first mindset > You understand failure modes Stack : Solidity + Foundry / Hardhat + Slither / Echidna 👉 3. Account Abstraction Wallet (Real UX) Build a minimal AA wallet with gas abstraction and recovery. What it proves : > You understand UX + protocol trade-offs > You’re future-facing Stack : ERC-4337 + Bundler + Paymaster + Frontend (React) 👉 4. DEX Analytics & MEV Visibility Tool Track swaps, slippage, MEV impact, and liquidity movement. What it proves : > Protocol-level understanding > Economic intuition Stack : Uniswap / DEX + Indexer + Data viz +Python / JS 👉 5. Cross-Chain Message Verifier Verify and visualize how cross-chain messages are validated and fail. What it proves : > You understand cross-chain risk > Architecture-level thinking Stack : Any cross-chain protocol + Event listeners + Fraud / verification logic 👉 6. Layer 2 Security Comparison Dashboard Compare trust assumptions of different L2s. What it proves : > You can reason about security models > You understand rollup designs Stack : Ethereum+ L2 docs + contracts + Visualization layer 👉 7. Onchain Governance Simulator Simulate DAO proposals, voting power shifts, and attack scenarios. What it proves : > Governance + incentive understanding > Systems thinking Stack : DAO frameworks + Token logic + Simulation scripts 👉 8. ZK Proof Demo with Real Use Case Not “hello world ZK” show proof verification in a real flow. What it proves : > You understand ZK beyond buzzwords > High-signal skill Stack : Circom / Noir + Verifier contracts + Frontend proof generation 👉 9. Formal Verification Case Study Formally verify one real-world contract and explain the results. What it proves : > Precision > Professional security mindset Stack : Certora / Scribble / Foundry + Write a human-readable report 👉 10. Blockchain Incident Post-Mortem Repository Analyze past hacks and explain why they happened. What it proves : > Deep learning from failure > Communication + technical clarity Stack : Real incidents + Diagrams + Clear write-ups 👉 (save it)
    Download
    184643120.5K
  21. Max Soul 🧱@0xMaxSoul
    Damn Toly, you're so wise even outside of crypto
    toly 🇺🇸 @toly
    @Zeneca Kids have been optimized by 4 billion years of evolution to extract the maximum amount of resources from their parents without killing the parents.
    001124
  22. toly 🇺🇸✓@toly
    Posts @Zeneca
    @Zeneca Kids have been optimized by 4 billion years of evolution to extract the maximum amount of resources from their parents without killing the parents.
    432141835.6K
  23. Max Soul 🧱@0xMaxSoul
    Max Soul 🧱
    RT @midenmonk: as OGs used to say, deplatforming is a real risk. X blocking Kaito and others is probably the right call from their side but also a reminder that whoever owns the platform holds all the power. Not your keys, not your crypto. Not your platform, not your business
    050953
  24. Max Soul 🧱@0xMaxSoul
    Max Soul 🧱
    RT @alive_: Privacy will be the most important moat in crypto. Why? Because secrets are hard to migrate. Everyone is launching a new "high performance" blockchain lately. But these chains are hardly different from one another. Blockspace is functionally the same everywhere. And with bridges that make moving between chains easy, that blockspace is now accessible *from* everywhere. Mercenary users and capital quickly arriving on a chain to farm an airdrop can leave just as quickly to farm the next one on another chain. The reality is that if your "general purpose" chain doesn't already have a thriving ecosystem, a killer application, or an unfair distribution advantage, there's very little reason for anyone to use it or build on top of it. Performance alone is no longer enough. Privacy is the one feature that everyone agrees is critical for the world’s finance to move onchain. It’s also the one feature that almost every blockchain that exists today completely lacks. For most chains, it has been little more than an afterthought until now. Privacy by itself is sufficiently compelling to differentiate a new chain from all the rest. But it also does something more important: it creates chain lock-in. Bridging tokens is easy, but bridging secrets is hard. As long as everything is public, it's trivial to move from one chain to another, thanks to bridging protocols like LayerZero. But, as soon as you make things private, that is no longer true. There is always a risk when moving in or out of a private zone that people who are watching the chain, mempool, or network traffic will be able to figure out who you are. Crossing the boundary between a private chain and a public one—or even between two private chains—leaks all kinds of metadata like transaction timing and size correlations that makes it easier to track you. Compared to the many undifferentiated new chains whose fees will likely be driven down to zero by competition, blockchains with privacy have a much stronger network effect. When you're on public blockchains, it's easy to transact with users on other chains—it doesn't matter which chain you join. When you're on private blockchains, on the other hand, the chain you choose matters much more because, once you join one, you're less likely to move and risk being exposed. This will create a winner-take-most dynamic. And because privacy is essential for most real-world use cases, a handful of privacy chains will own most of crypto.
    01590505K
  25. Max Soul 🧱@0xMaxSoul
    A reminder to myself, never a bad idea
    toly 🇺🇸 @toly
    Every ceo needs a 6 week plan and an 18 month plan. The 18 month plan A) If the market totally collapsed like 2020: 1) what’s the product that the company needs to hyper focus on for the next 18 months. 2) what’s the team to do it 3) why isn’t this what the company looks like right now? B) The 6 week plan 1) what is driving profits/revenue/user growth? 2) how can we improve them in the next 6 weeks In a bear market B is gonna feel like beating a dead horse and you need to focus more on A
    001139
  26. toly 🇺🇸✓@toly
    Every ceo needs a 6 week plan and an 18 month plan. The 18 month plan A) If the market totally collapsed like 2020: 1) what’s the product that the company needs to hyper focus on for the next 18 months. 2) what’s the team to do it 3) why isn’t this what the company looks like right now? B) The 6 week plan 1) what is driving profits/revenue/user growth? 2) how can we improve them in the next 6 weeks In a bear market B is gonna feel like beating a dead horse and you need to focus more on A
    1076992252K
  27. Show more posts