if this ends up being limited to just the current term (as I think we should do), then we could remove the option of doing it in the past all together and just allow linear searches

yes, that _sortition duplication is temporary, it was a quik work around for stack too deep issue, and I was waiting as you said to see if we really need both options or stick to just one

yes, that _sortition duplication is temporary, it was a quick work around for stack too deep issue, and I was waiting as you said to see if we really need both options or stick to just one

Is truffle supposed to compile dependencies? If so, why? security? 😕
(trying to update truffle to v5 which uses solc-js v0.5 and the compilation fails)

Moving to truffle@5 is going to be a longer process across the entire development pipeline

@danielconstantin Moving to truffle@5 is going to be a longer process across the entire development pipeline

I imagine we could start doing it for the boilerplates though

You should also be able to specify the solc version (it will have to be 0.4.24) in the truffle config

This is super cool: https://github.com/cgewecke/eth-gas-reporter/blob/master/docs/codechecks.md

Thanks for sharing it

A nice solidity build tool from a Nest grantee, @mcormier: https://github.com/macor161/quantal/

Hey thanks Brett! :)

Still a few months to go before production-ready though

wow, this is really cool @mcormier !!! So long waiting for nice error output! (So many times I have done truffle compile | grep Error, haha)

@bingen This is precisely because I was tired of doing truffle compile | grep Error that I started the project haha

It was basically a simple truffle-compile fork at first, but then I stumbled upon a few optimizations to speed up the compilation process.

This is quite cool for managing solc versions via docker: https://github.com/crytic/solc-select

The key things we should have this agent app do:

• Send / receive a eth transfer
• Send / receive a token transfer
• Contract invocation to another installed app (e.g. create a vote)
• Contract invocation to another org’s app (e.g. create a vote / vote)
• Contract invocation to an arbitrary contract
• Contract invocation that causes multiple tokens to be sent / received (e.g. atomically swap tokens for ETH)

• Should we keep register unprotected as it is now or only allow an ‘owner’ to register new versions? Once you have tagged a certain code hash you cannot re-tag it, so the only risk would be someone registering a version before us, but i think that is pretty low risk (specially if this is published to APM and we can update it if we are trolled) and easier to maintain.

• Where should we put it? It feels weird for it to be on aragonOS, so I’d lean towards a new repo