17 Jul 2019 |
bridge-bot | <bingen> wow, this is really cool @mcormier !!! So long waiting for nice error output! (So many times I have done truffle compile | grep Error , haha)
| 21:29:41 |
18 Jul 2019 |
bridge-bot | <mcormier> @bingen This is precisely because I was tired of doing truffle compile | grep Error that I started the project haha
| 02:56:46 |
bridge-bot | <mcormier> It was basically a simple truffle-compile fork at first, but then I stumbled upon a few optimizations to speed up the compilation process.
| 02:57:23 |
22 Jul 2019 |
bridge-bot | <sohkai> This is quite cool for managing solc versions via docker: https://github.com/crytic/solc-select
| 10:27:30 |
25 Aug 2019 |
| @polviebolci3:matrix.org joined the room. | 15:32:29 |
| @polviebolci3:matrix.org left the room. | 15:32:37 |
29 Aug 2019 |
bridge-bot | <sohkai>@jorge We’re moving along quite quickly on the Agent app’s frontend, but if you or @facuspagnuolo have a bit of time, it’d be great if we could get an org with one installed on rinkeby to make testing a bit easier.
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)
| 18:41:08 |
bridge-bot | <facuspagnuolo>I have a trust DAO on rinkeby we can use if it helps | 18:50:39 |
bridge-bot | <facuspagnuolo>We simply need to grant the Agent app all the permissions you want to test I think | 18:51:14 |
bridge-bot | <facuspagnuolo>https://rinkeby.aragon.org/#/trust-dao/permissions | 18:51:16 |
3 Sep 2019 |
bridge-bot | <jorge>@sohkai @facuspagnuolo @bingen did an initial spike for the version oracle for detecting proxy versions: https://gist.github.com/izqui/7dba72aedef31e2e1621f39c388577b7 | 10:44:41 |
bridge-bot | <jorge>some aspects to decide: | 10:44:54 |
bridge-bot | <jorge>
- 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.
| 10:46:52 |
bridge-bot | <jorge>
- Where should we put it? It feels weird for it to be on aragonOS, so I’d lean towards a new repo
| 10:49:05 |
bridge-bot | <sohkai>New repo sounds good; I’d lean towards making it protected; this would ideally be something that gets updated along with Aragon client versions in the line as AGP-28 | 10:55:46 |
bridge-bot | <jorge>@sohkai about to release aragonOS 4.3, should we merge this in as well? https://github.com/aragon/aragonOS/pull/540 | 13:24:23 |
bridge-bot | <sohkai>No, let’s not. SafeERC20 isn’t used by the proxies at all. | 13:26:08 |
bridge-bot | <jorge>initial spike for the version oracle: https://github.com/aragonone/version-oracle/pull/1 | 17:58:11 |
bridge-bot | <bingen>For reference, in case we eventually want to discuss this:
https://github.com/bingen/aragonOS/commit/ac3116c3016a194e9bf3d7b8a5d3261474dfa306
(I didn’t push it to main repo because it’s just a test and didn’t want to clutter it) | 20:56:11 |
22 Oct 2019 |
bridge-bot | <bingen>Interesting how Compound documents error messages:
https://compound.finance/developers/ctokens#ctoken-error-codes
(Thanks @ajsantander for the link!) | 16:50:14 |
23 Oct 2019 |
bridge-bot | <sohkai>For those using Visual Studio Code, this solidity-auditing extension may be interesting (it’s made by one of our auditors): https://marketplace.visualstudio.com/items?itemName=tintinweb.solidity-visual-auditor | 09:29:27 |
1 Nov 2019 |
bridge-bot | <sohkai>Looks like the istanbul hardfork is finalized: https://eips.ethereum.org/EIPS/eip-1679 | 18:22:52 |
15 Nov 2019 |
bridge-bot | <bingen>No, I’m not aware of the timeline, but I don’t think we want to wait anyway. Even with small changes, at some point we talked about being cautious and not using a too recent version. | 08:58:53 |
bridge-bot | <sohkai>Although the latest solidity versions do look like they contain some bug fixes | 14:21:53 |
18 Dec 2019 |
bridge-bot | <sohkai>@bingen @facuspagnuolo solidity 0.6.0 just got released: https://github.com/ethereum/solidity/releases/tag/v0.6.0 | 01:21:50 |
29 Jan 2020 |
bridge-bot | <sohkai>solc 0.6.2 (https://github.com/ethereum/solidity/releases/tag/v0.6.2):
Furthermore, interfaces can now inherit from interfaces, making them even more useful for specification purposes.
😍 | 17:47:52 |
bridge-bot | <sohkai>Also:
General: Raise warning if runtime bytecode exceeds 24576 bytes
cc @bingen ;) | 17:49:16 |
30 Jan 2020 |
bridge-bot | <bingen>https://twitter.com/3esmit/status/1222794628614828032?s=19
Do we need to update the address for our templates? | 08:41:17 |
bridge-bot | <sohkai>@bingen Eventually yes, but we can wait to manually migrate after the ENS team has finished their migrations :). | 11:29:19 |
3 Mar 2020 |
bridge-bot | <bingen>Interesting. Do you know what is the syntax? Is it this.functionName.selector or ContractName.functionName.selector . I guess it’s the latter, as this is not compile-time constant. | 08:14:49 |