Ellaism Dev Meeting 10/03/2018

[11:01 PM] ellaismer: @here Our dev meetings this week starts now.
[11:01 PM] Brokebeard: Hello everyone
[11:01 PM] IaMaBeAsT: Howdy all
[11:01 PM] Riddlez666: im alive lol barely
[11:02 PM] TBates76: HI.. what day is this?
[11:02 PM] Brokebeard: I'm  going through online traffic school.. Mandatory 4 hours of reading then exam -.-
☹2
[11:02 PM] Brokebeard: damn traffic cameras...
[11:04 PM] easy: Hello
👋1
[11:04 PM] TBates76: Ok this is now the weekly meeting any other discussions needs to goto general(edited)
[11:07 PM] TBates76: !RSVP YES
[11:07 PM] ellaismer: One thing I really want to discuss is about our geth client. Our current geth fork is based on ETC, but many devs have suggested that we create one based on ETH due to various compatibility issues. The problem we have right now is related to unused code -- our chain's config is similar to ETC, and if we blindly just use ETH's fork, we can get it working, but it will contain many unused codes. So what I'm thinking about is to fork ETH's version, but add multi-chain support -- make it by default support ETH/ETC/ELLA three networks. We accomplish three things by doing this:

1. We solved our problem that we lack geth compatibility fork for ELLA.
2. ETC is also suffer from the same problem. By doing this, we also help ETC users who use geth, and it will likely gain some more users for us.
3. If we make the changes minimal and only related to multi-chain support. We can attract those who want to use geth on multiple networks.
[11:08 PM] osoese: @ellaismer music to my ears - here to help
[11:10 PM] osoese: also - please take this as humor as that is what I mean, but I think our next block mining algo can be

[11:11 PM] Riddlez666: lol
[11:11 PM] ellaismer: And because we have limited manpower, what I would suggest is to do this:

1. We keep https://github.com/ellaism/go-ellaism using ETC's fork, and continue to merge ETC upstream patches. This way, we don't break anything for existing go-ellaism users.
2. We use https://github.com/ellaism/go-ethereum, which was started by @MakeMoneyOz - ellaismpool.com, as the base for multi geth version based on ETH.
3. We make the changes minimal -- we don't change golang import paths (keep it github.com/ethereum/go-ethereum). This makes it easier to merge upstream ETH changes.
4. I created a team called "multi-geth" for ellaism/go-ethereum, if you want to help developing multi-geth, please just ask me to add you to the team.
5. All changes for multi-geth go through pull requests. Master is set as protected branch.
GitHub
ellaism/go-ellaism
go-ellaism - Go language implementation of the Ellaism protocol

[11:13 PM] ellaismer: How @DEVS like this? Is there anything I might have missed?
👍1
[11:13 PM] TBates76: We could also put this out to the other coins for dev help
[11:13 PM] jal3inc: Good morning :sunny:️
[11:14 PM] TBates76: Aka eth/etc
[11:14 PM] osoese: @ellaismer agreed by me and I like #3 especially because that was tough to do when @Riddlez666 and I worked on this
[11:15 PM] ellaismer: @TBates76 Yeah that's a good idea. I think we can first finish a version, it will better help to gain dev support.
[11:15 PM] osoese: (the import paths)
[11:15 PM] ellaismer: @osoese Yeah great. :smiley:
[11:16 PM] ellaismer: And by the way, there're tools to help you to change import paths (like gomvpkg), but it will be a problem when merging upstram changes.
So I'm glad to know we like keeping github.com/ethereum/go-ethereum import path. :smiley:
[11:18 PM] osoese: well, if there is a tool for that I will take a look because search and replace wasn't the answer and there are a lot of updates - I think we got close but never got every path updated in my last attempt
[11:19 PM] osoese: gave up and forked a version keeping the paths to edit instead - so glad you are open to that
[11:22 PM] ellaismer: And @DEVS, as we are collaborating using PRs, If you see new PR in github.com/ellaism/go-ethereum, please review the PR. Click "changes" tab, and click "Review Changes". If you think everything look okay, please select "Approve", and click "Submit". :smiley:(edited)
[11:23 PM] Riddlez666: We are getting farther on setting up the exchange no date on when any test will happen as its a pretty big undertaking. But last i check 59 people signed upto the mailing list for info.
ellahaze3
[11:24 PM] ellaismer: Okay. My only agenda today is multi-geth, and let's just carry out the project first.
@here If you have something else to discuss, now it's time to raise your voice. I'll continue to be here answering questions.
[11:26 PM] Riddlez666: Ive been busy this week with some real life backlog and the exchange filling up the other time so i have nothing other than that myself
[11:26 PM] jal3inc: @Riddlez666  :smiley:

[11:26 PM] Riddlez666: 70 people now lol
[11:27 PM] osoese: I can link to the alpha wallet - which is definitely in alpha
[11:27 PM] osoese: https://github.com/osoese/Opal-Alpha-0.0.1
GitHub
osoese/Opal-Alpha-0.0.1
Opal-Alpha-0.0.1 - Ellaism Opal Wallet Alpha 0.0.1

ellamoon1
ellahaze1
💯1
[11:27 PM] TBates76: I would like to discuss the roadmap this geth fix will that help move along the roadmap and help with BTC relay
👍2
[11:28 PM] jal3inc: Just wanna say thank u to all the devs that have taken the time to get me up to speed with things. You guys are great!
😘1
[11:29 PM] osoese: @jal3inc yw
[11:30 PM] osoese: @ellaismer youa re probably busy with geth and work - but if you are interested in the egem project we are working under @Riddlez666 direction and could definitely use any extra eyes on the project - we have one exchange server and 2 coin servers going - getting them all to talk is coming together but help is always apprecaited
[11:31 PM] jal3inc: @ellaismer  sent you over that info to your inbox check it out when u have a chance.
[11:31 PM] TBates76: @osoese wouldnt the multi chain geth help with that?
[11:31 PM] Riddlez666: ehhh
[11:31 PM] Riddlez666: not with what we are doin
[11:31 PM] osoese: @TBates76 this one really has nothing to do with that atm
[11:32 PM] jal3inc: From exchange side of things id imagine no difference really
[11:32 PM] osoese: BUT - the geth update very important!!
👍1
[11:33 PM] ellaismer: @osoese Yeah I'm glad to help.
😀2
ellahaze2
[11:35 PM] Riddlez666: I have a feeling decentralized exchanges are just another hype word as it will have a single point of failure also.
[11:36 PM] Riddlez666: My point being if its cryptopia or cryptobridge you still need a support team if shit screws up which in itself is not a decentralized exchange.
👍3
[11:37 PM] osoese: @Riddlez666 was going to politely disagree until I saw 2nd comment
[11:37 PM] Riddlez666: also its not a complete system if you need a support team to fix screwups...lol
[11:38 PM] Riddlez666: im having trouble seeing the vision of decentralized exchanges also
[11:38 PM] Riddlez666: sorry im brain storm rambling
[11:39 PM] jal3inc: @Riddlez666  im with u on that

[11:41 PM] osoese: okay - I don't have anything else for today, but if anyone wants to give the wallet a try - just know there are bugs - its on meteor (at this time) and @MakeMoneyOz - ellaismpool.com @jal3inc @Riddlez666 are all helping me put together install instructions but it might not be complete as of yet. If you need help just post a message in #development
[11:42 PM] Riddlez666: Bitshares for example they have there own chain with a bunch of exchanges tied to it but can you do trades with just the bitshares client? no you cant you need a 3rd party system built on top of it.
[11:42 PM] ellaismer: @osoese I got the SMTP user for you as well, for osoese@ellaism.com. Check your Keybase!(edited)
[11:43 PM] osoese: ha! thank you @ellaismer
[11:46 PM] osoese: @Riddlez666 the core of a decentralized exchange is a trade. That trade happens whenever you send coins to someone for like kind value in something else. If we just get that fore functionality embedded in a wallet/app that connects to peers instead of central server then it can grow into a decentralized exchange. This would then be independent of all government or corporate supervision. If the software is open source then communities can handle support.
[11:50 PM] ellaismer: Looks like we're having a short meeting today as well! If there's no more things to discuss, let's close?
[11:51 PM] TBates76: Roadmap
[11:51 PM] TBates76: will there be a roadmap with dates for completion?
💯1
[11:53 PM] ellaismer: Hmm @TBates76 probably not. Deadlines are always missed everywhere. And as said before, it's also important to have a  focus on quality.
To be honest, the roadmap you see at https://ellaism.org/roadmap has no dates on purpose, because that's not how software development (especially open source software development) works.
Ellaism
2018 Roadmap
Ellaism Core’s Roadmap in 2018. A stable Ethereum network without pre-mine or dev fees.

[11:54 PM] TBates76: I understand
[11:55 PM] Riddlez666: all dates do is stress and usually end up releasing shitty code
💯1
[11:55 PM] TBates76: I am just thinking of making something for people to see whats being worked on atm
[11:56 PM] Riddlez666: ahh the meta page i need to update
[11:56 PM] Riddlez666: but shows in progress stuff
[11:57 PM] ellaismer: @TBates76 I think we try to use the monthly update for that purpose. I understand there may be better ideas, though.
March 11, 2018
[12:01 AM] TBates76: thats all I can think of atm
[12:02 AM] TBates76: :hammer:  meeting adjourned
[12:02 AM] TBates76: (closest thing to a gavel)
[12:02 AM] ellaismer: !rsvp set-date 17 Mar
[12:02 AM] BOTRSVPBot: RSVP date set to 17 Mar.
[12:03 AM] ellaismer: !rsvp clear