| 3 Feb 2019 |
 Asgeir | 
Download Screenshot 2019-02-03 at 22.18.29.png | 21:19:07 |
 dOrgJelli | Lel | 21:19:52 |
| Asgeir | hmm... But something must be live, because of Genesis Alpha | 21:21:13 |
| dOrgJelli | Is it hard coded in alchemy? | 21:25:51 |
| Asgeir | Will check | 21:26:08 |
| Asgeir | Check this: https://alchemy.daostack.io/daos | 22:29:34 |
| dOrgJelli | "AsgeirDAO" lmao | 22:57:09 |
| 4 Feb 2019 |
 cd10012 | dOrg | Asgeir: do you mind explaining how you did that lol | 14:07:33 |
| Asgeir | cd10012: https://alchemy.daostack.io/create-dao | 14:44:53 |
| Asgeir | 😛 | 14:44:58 |
| cd10012 | amazing when did they add this!? | 14:47:27 |
| Asgeir | I think it's been there all along :P But I have not checked the commit log | 14:52:23 |
| 5 Feb 2019 |
| dOrgJelli | nice graph-node (graphQL) primer: https://github.com/graphprotocol/graph-node/blob/master/docs/graphql-api.md | 00:27:47 |
| 6 Feb 2019 |
| Asgeir | Today I have been working on getting the DAOcreator functional on mainnet.
I have had some progress. The current state is: it fails while deploying (after the first transaction has completed). I have been trying to replicate how it is done for the DAOcreator in Alchemy, but I have not managed to get it fully working yet. I have created this branch: https://github.com/dOrgTech/dOrg/commits/main-net-support where I have been experimenting if you want to take a look.
I will continue exploring this tonight or tomorrow. | 14:49:15 |
| dOrgJelli | 👏 awesome work Asgeir
I saw that as well, the creator in alchemy only uses 1 tx, and not 3... the code paths & method calls must be different | 15:47:20 |
| Asgeir | I managed to deploy a simple DAO on mainnet through our DAOcreator now 😃 . See the branch mentioned above for the WIP. | 16:13:23 |
| Asgeir | dOrgJelli: Have you goon through the DAOcreation process in Alchemy on mainnet? I thaugth I did 3 transactions when I set it | 16:15:07 |
| Asgeir |
| 16:15:27 |
| Asgeir | I will complete this work later today or tomorrow | 16:16:23 |
| Asgeir | 
Download Screenshot 2019-02-06 at 17.07.36.png | 16:16:52 |
 orishim | We have lift off 🎉👏🙏🎉 | 16:28:52 |
| Asgeir | Still, more work to be done before its usable for end users | 16:59:47 |
| dOrgJelli | Just had a chat with Adam, here are the takeaways:
- DAOstack & TheGraph had a call where they discussed the dynamic reading problem. TheGraph is very aware, and thinks they'll have a first implementation of it come March.
- Alchemy's master branch is where we should fork from for the DAO creator. It will be very slow though because of no caching.
- Alchemy's dev branch is where they've added caching & are going to create the new front-end for alchemy earth.
- Arc is on code freeze.
- DxDAO is live, and he wants us to hack it. Deadline is the 16th I believe.
- He's aware lots of people want their own DAOstack DAOs, and says caching is the main thing blocking it.
- He suggested we play around with TheGraph, better understand the limitations, and also reach out to the team. They're very responsive and always looking for outside developers to chat with.
- He liked the idea of wrapping the client library with React components to make app integrations easier.
| 17:43:21 |
| dOrgJelli | Also they're continuing to try and open source their internal developments as much as they can. Here's a good first step, a public task trackinmg board for alchemy instead of their private trello they used to use: https://github.com/daostack/alchemy/projects/2 | 17:45:33 |
| Asgeir | That's a lot of useful information. Thank you, dOrgJelli | 19:39:58 |
| 8 Feb 2019 |
| orishim | curious if this is useful to us: | 19:24:20 |
| orishim | https://embark.status.im/ | 19:24:20 |
| orishim | either as a development environment for building DAOcomponents, DAOactions | 19:24:41 |
| orishim | or as a model for what the outcome of those might look like | 19:24:54 |
| orishim | like we could build a tool like embark | 19:25:07 |
