lukechilds
/
vote2018
mirror of https://github.com/lukechilds/vote2018.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Merge pull request #51 from libscott/master 

libscott proposal
patch-1
Mihail «Kolo» Fedorov 7 years ago
committed by GitHub
parent
650677d85b 8ba9ef812e
commit
166df97e95
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 43 additions and 2 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 5
      README.md
  2. 40
      proposals/libscott/README.md

5
README.md
View File

@ -24,6 +24,7 @@ Data is coming soon - everything is hand crafted and manually verified. Please,
| kashifali | [proposal](./proposals/kashifali) | | | + | | kashifali | [proposal](./proposals/kashifali) | | | + |
| komodominingpool | [proposal](./proposals/komodominingpool) | | | + | | komodominingpool | [proposal](./proposals/komodominingpool) | | | + |
| komodopioneers | [proposal](./proposals/komodopioneers) | | | + | | komodopioneers | [proposal](./proposals/komodopioneers) | | | + |
| libscott | [proposal](./proposals/libscott) | **EU** **SH** | | + |
| lukechilds | [proposal](./proposals/lukechilds) | | | + | | lukechilds | [proposal](./proposals/lukechilds) | | | + |
| lumberscout | [proposal](./proposals/lumberscout) | | | + | | lumberscout | [proposal](./proposals/lumberscout) | | | + |
| meshbits | [proposal](./proposals/meshbits) | | | + | | meshbits | [proposal](./proposals/meshbits) | | | + |
@ -41,8 +42,8 @@ Data is coming soon - everything is hand crafted and manually verified. Please,
## How to submit perfect proposal ## How to submit perfect proposal
- Proposals and corrections are submitted via pull request to master branch of this repo. Your proposal should be a **lowercase named** subdirectory inside `proposals` dir with `REDAME.md`. - Proposals and corrections are submitted via pull request to master branch of this repo. Your proposal should be a **lowercase named** subdirectory inside `proposals` dir with `README.md`.
- It **should** have all particiapting regions explictly stated and have transparent wallets for each. Regions are named: AR, NA, SH, EU. There is no regions named AU, AE, SE etc. Good candidates also provide z-address. - It **should** have all participating regions explictly stated and have transparent wallets for each. Regions are named: AR, NA, SH, EU. There is no regions named AU, AE, SE etc. Good candidates also provide z-address.
- It **might** have pubkeys (btcpubkey) attached to each wallet. Failure to provide pubkey timely might end up loosing spot. - It **might** have pubkeys (btcpubkey) attached to each wallet. Failure to provide pubkey timely might end up loosing spot.
- It **should** have your slack contact nickname(s) visible and noticable. - It **should** have your slack contact nickname(s) visible and noticable.
- Your propoposal **must** have separate section named `Disclosure` where you should disclose any impacting relationships with other candidates, your status as a team member (if you're invited in team chat) and nodes you're currently operate as auto re-elected. - Your propoposal **must** have separate section named `Disclosure` where you should disclose any impacting relationships with other candidates, your status as a team member (if you're invited in team chat) and nodes you're currently operate as auto re-elected.

40
proposals/libscott/README.md
View File

@ -0,0 +1,40 @@
# Libscott Notary Node proposal
![icon](https://avatars2.githubusercontent.com/u/125019?s=52&v=4)
## Who am I?
* Programmer of 11 years.
* Proud to be working with Komodo since 2017.
* Specialist in smart contracts, state machines, data structures etc.
## What am I doing?
I am the author of two implementations of interledger crypto-conditions, in Haskell and C. I have also done the first integration of Crypto-Conditions into the bitcoin scripting language; for Komodo! This was done with the addition of a [script opcode](https://github.com/libscott/komodo/blob/7d937f290e08522beaf10d6ffe237a756a06361b/src/script/interpreter.cpp#L939).
I am designing a [protocol](https://github.com/libscott/hoek/blob/spec/specs/bet.md) for cross chain contract settlements (ie to enable [chips](https://bitcointalk.org/index.php?topic=2078449.0;all)).
This protocol will open up a wide range of smart contract possibilities, with applications running on Komodo asset-chains. Additionally, the inclusion of Crypto-Conditions into the Komodo network will provide a high degree of connectivity via the rest of the crypto ecosystem, principally via Ripple's InterLedger protocol (ILP). ILP is a cross chain settlement layer for atomic swaps.
In case you are wondering, the key difference between atomic swaps and cross chain contract settlements is that contract settlements are not atomic, they are backed by on-chain code to verify contract states.
## Why vote for me?
* Running a notary node will give me a broader experience of the Komodo platform.
* The additional income will help me to support myself.
* I am excited about Komodo and truly looking forward to seeing what we can achieve!
## Regions
* SH: `REEGE6drFqGLpxiA1mhfcb5R9MndnaD1cy`
* EU: `RVMtoPmL8SiHCXSceMmxwpScAhDgsVvTZc`
## Node specs
Nodes will be optimised for connectivity and latency rather than CPU power, however, in the case of winning I will run multiple redundant nodes per region.
## Disclosure
Outside collaborator on Komodo, as detailed above!
Thank you!
Write Preview
Loading…
Cancel
Save