(っ⬤ω⬤)っ securityDAO.wasm 🪐

• @CosmWasm smart contract audit & code review
• ⛓ validator & @cosmosibc relayer pentest
• responsible disclosure
• incident response

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

@JunoNetwork At this pivotal junction of our subDAO transition, this @RnDAO__ research report is a great read to understand the various subDAO patterns out there https://t.co/V3HFZREcvQ

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

Thank you for feedback thus far, @JunoNetwork. Per Prop 25, Junø Community DAO is wholly the admin, instantiator, and funds owner of all subDAOs.
dao-contracts v1 offers great flexibility w/ modular governance, and your feedback will inform our suggestion!
https://t.co/rQgcnXP2r7

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

@ekez___ @JunoNetwork @SecurityOak @strangelovefund @notionaldao @HackJuno outside of audits alone, this new structure can allow for existence of an on-call rotation and concrete on-chain commitments to what a contribution of someone needs to be and corresponding rewards (as well as penalties for missed SLAs!) 🕹 #gamify

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

@ekez___ @JunoNetwork @SecurityOak @strangelovefund @notionaldao @HackJuno ✅ added to the Commonwealth post https://t.co/ZVzdYKRq8G

audits + formalized responsibilities and incentives

We plan to welcome everyone who can contribute, and reward those whose code we use (incl. in disclosure), and use the new on-chain governance format of subDAO #Prop25

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

@ekez___ @JunoNetwork @SecurityOak @strangelovefund @notionaldao @HackJuno Fantastic points, @ekez___! 💚 Among many:

- transparency in compensation structures for ongoing contributions (like on-call SOC type roles)
- enfranchisement of community into governance over decisions that affect them and have trade-offs to consider
- meritocracy for newcomers

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

@JunoNetwork @SecurityOak @strangelovefund @notionaldao @HackJuno We would like to hear your feedback and follow the best practices of creating a public good organization!

Discuss in comments here and on Commonwealth (no backroom Discord / Telegram please):

https://t.co/JLQXBRLYfP

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

@JunoNetwork @SecurityOak @strangelovefund @notionaldao @HackJuno We would like to hear your feedback and follow the best practices of creating a public good organization!

Discuss in comments here and on Commonwealth (no backroom Discord / Telegram please):

https://t.co/JLQXBRLYfP

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

@bmorphism @blockpane @JunoNetwork Here is what we had to say at the time:

https://t.co/Av0j9UHEyL

[barton.wasm @bmorphism]

Great writeup from comrade @blockpane setting the new standard for forensics quality in @JunoNetwork!
🫡🪐

Even as someone involved in @security_dao validator response and malicious contract analysis, I have learned new things. Give it a read ⬇️✨
https://t.co/UnXoHiWej7

[WalletConnect @WalletConnect]

v2.0 of our Sign API offers many improvements over v1.0, including:

⛓️ Simultaneous multi-chain support

🖇️ One-time pairing for multiple sessions

🛠️ Wallet API permissions system

You can read more about it in @pedrouid's blog post here: https://t.co/7flVkbvxoT

🧵 2/5

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

https://t.co/tQZ5lHG47I

[Anoma @anoma]

#privacyevolution panel:

"ZKPs & other crypto schemes to solve hard problems in #Web3"

- @drakefjustin | @ethereum Foundation
- @cryptodavidw | @o1_labs/@MinaProtocol
- @BrianRetford | @RiscZero
- @1HowardWu | @AleoHQ
- @cwgoes | @anomanetwork

Moderator: @gakonst | @paradigm

[Thyborg @Thyborg_]

All these opportunities are born the fact that:

1- a block can only contain a limited number of transactions
2- block producers have autonomy in selecting pending txs

These pending (i.e unconfirmed) transactions are stored in an off-chain location called the mempool

[Mike Purvis 🛡️ | mike.near @mikedotexe]

ever just get in the documentation zone?
these aren't big contributions, but I am sniping every broken link in @CosmWasm and hunting down the proper resources

it's actually been a great way to learn. i'm fired up!

[Inference @inference_ag]

A new security assessment has been completed for Anoma MASP circuits. The report can be found at: https://t.co/1YbKrxRot3.

[Strangelove @strangelovelabs]

Great workshop on Cosmos Validator best practices from @gnudrew25 @DanDefiant @nullMames taped last week. Learn how to run a validator!

https://t.co/PKDMtWRN5Q

[Axelar Network @axelar]

The first Axelar Learn AMA, a weekly series of technical talks on cross-chain communication, kicks off this Thursday with a live walk-through of the Axelar tech stack led by co-founder @sergey_nog. Join us at 5pm UTC & bring your questions. https://t.co/YUqzTLzymd

[barton.wasm @bmorphism]

@L1am_Crypto 3. @CosmWasm contract code is a growing part of programming in the Cosmos SDK and greater #Interchain ecosystem, go check out the introduction by @ekez___ and delightful series by @frey_needlecast @callum_and1
𝚌𝚠_𝚖𝚞𝚕𝚝𝚒_𝚝𝚎𝚜𝚝 is your friend!
https://t.co/CXIADubiAR

[(っ⬤ω⬤)っ securityDAO.wasm 🪐 @security_dao]

https://t.co/fgDZqsN6z0

[Dan Lynch @danlynch]

are you a frontend developer in #web3? in the cosmos? I'm crowdsourcing ways to improve the developer experience and would appreciate your ideas/feedback for how to develop frontends and FE tooling in cosmos https://t.co/M2E3JBWnZ2