User:Lex Berezhny/Log/2018

Feb 10, 2018

• moved osedev from https://github.com/damoti/osedev to its final place at https://github.com/osedev/osedev, also moved the osedev-workbench to the new org and renamed it to just workbench.
• created a new logo for osedev using Teko font.

Doing more brainstorming on a OSE Coin as an ERC20 token... another feature to solve security concerns could be that the phase-in/phase-out period is 30 days instead of 15 days and everyone who is currently a member also will have 'voting' ability to change the public key from which the active participants update is performed.

• The solidity contract would keep a table of public keys from which member lists can be submitted.
• Existing members can 'vote' on which public key is allowed to submit member lists. Voting is an ongoing process, with vote outcome impacting the daily submission of member list. (You'd only have to vote once and after that your vote is re-used until you change it.)
• Since phase-in/phase-out is 30 days, there is plenty of time to change the public key in case the key, the server or some part of the process is compromised before the effects of the compromise would start to manifest.

Every day when a server submits a member list, signed by a servers private key, the Solidity contract will check that the public key currently with the most votes is a match for the signed list, if the key matches then dividends are payed out, if the list is not correct then it's simply ignored.

In case I'm hit by a large bus or win a giga nugget lottery (and retire to an island with servants, gold bling and vomitoriums... ridiculous right?) it would be possible to replace me and osedev.org in a day:

• select a new domain for osedev.org
• check-out osedev from github and set it up
• generate a new public/private key pair for your server
• ask all existing ose dev members to vote for your public key
• start submitting member list from your server
• all systems back to normal!
• and you still have 29 days left to resolve any issues before dividend payouts for existing members are affected.

As an extra precaution, an independent service on another computer under someone elses control would have a script running that would pull in the most recent member list that was added to the blockchain and diff it against the previous one, if there is a change it would generate an email to a group mailing list saying someone has joined or has left the member list. If an unknown/unexpect person gets added or someone who shouldn't have been removed gets removed, then we'll notice and can do something about it before the change is permanent (in 30 days).

Feb 9, 2018

• ethereum gas fees (currently $0.035/transaction): https://ethgasstation.info/
• upon further reflection on the potential of using ERC20 tokens I'm thinking now that the fees will just discourage use of the coin. if you want to do any kind of transaction, such as pay / tip someone OSE Coin you'd have to come up with $0.035 in ether gas ontop of whatever you are tipping in OSE Coin... on the other hand, is $0.035 per transaction a reasonable fee in order to have a decentralized / fully operational crypto currency network today at our disposal?
• looks like there is a solution to above problem: https://github.com/ethereum/EIPs/issues/865 someone still has to pay the ethereum fees but it can be done as a service by some enterprising individual, they'd basically be selling ethereum on demand for OSE Coin per transaction, if OSE Coins start to have value than this would be a good business.

Feb 8, 2018

I've been thinking about Duniter and how it'll be years before it's fully tested and usable by communities outside of the original G1 currency and it occurred to me that it may be feasible to build OSE Coin on top of ethereum as a ERC20 token... only downside to this is that we'd have to pay ether as gas for various transactions. It would keep the dividend concept from Duniter but payouts would happen inside of an ethereum contract; the list of people to payout would be retrieved daily from an oracle who further retrieves it from osedev.org.

We can add various security precautions in case osedev.org is hacked, for example, the smart contract would require that a persons public key is published 15 days in a row before payouts begin and there is a 15 day phase out period after a persons public key stops appearing in the list (it does not appear in list for 15 days straight). This way, if anything happens to osedev.org there will be 15 days to resolve it while payouts continue as normal and to remove a malicious users public key from the list before payouts start (or add someone who was maliciously removed).

By using an ERC20 token it will be significantly easier to re-use all of the existing ethereum infrastructure and to get onto exchanges. This would be the fastest way to actually have a real OSE economy.

The list of public keys would be generated based on a combination of useful factors: total hours logged, CAD model changes, reviews/confirmations from other members as to a dev contributions, etc. The list generating function would continue to evolve to reflect lessons learned, taking into account special exceptions to the normal indicators, etc.

This has the best of both worlds:

• As an ERC20 token it will live on it's own as a known and accepted standard coin system that works with all ethereum wallets. We gain both by having an existing code base to build on and the reputation of ethereum.
• As a dividend system based on a list of public keys that we manage and maintain it has the "human" aspect of determining how we grow the community and help each other to build the future.

I still need to figure out what the cost would be in gas to run such an oracle driven ethereum dividend ERC20 token but I'd be willing to fund the initial gas account until things take off and more people would be willing to sponsor this. Probably it'll be $1/day to keep it running, not including what individuals pay for gas to actually use the tokens as currency.

Feb 4, 2018

• tried to figure out strange license bug on github where it wouldn't recognize the GPL license of osedev
• added videos to previous dev meetings and update the current meeting with new google slide deck

Jan 27, 2018

• incorporating core-xy concept in my super simple 3d printer design by having the corner pieces also hold the motor
• the x and y motors need to be offset vertically so that the belts don't have issues crossing
• vertical offset concept inspired from archived fabtotum blog post
• openscad files used during prototyping: https://github.com/eukreign/microfactory
• progress:

Jan 20, 2018

• working on a simpler frame for 3D printer (re-using the universal axis rods for the frame instead of CNC cut steel sheets)
• giving OpenSCAD a go instead of FreeCAD as it's much faster to prototype with:

Jan 14, 2018

• researching projects for when I get my Prusa i3 Mk3 next month:
  • User:Lex_Berezhny
  • User:Lex_Berezhny/Microfactory
  • User:Lex_Berezhny/Factory

Jan 6, 2018

• proposal for herox for the drill
• Small Aluminum Part Machine
• finished (audiobook) Bold by Peter Diamandis per Marcin's recommendation, lots to think about...