Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Howto publish a Slates for Delegates  (Read 355 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12280
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Howto publish a Slates for Delegates
« on: January 05, 2015, 03:31:49 PM »

Hey there,

I'd like to see many more (managed) slates among the elected delegates to build a web-of-trust using delegate slates such as delegate.xeroc.

Why?
The advantage of having several trusted sources of slates are:
 - users have no need to evaluate 101 delegates
 - if I trust delegate xyz .. and the delegates (how is supposedly connected to some of the other delegates) trust delegate abc, why shouldn't I?
 - assuming delegate uvy disappoints (fraud, misuse, reliability, ...) removing it from slates would directly affect all future transactions made via "as delegates recommend" - firing a delegate should be easier that way.

Helper script:
I published a script (originally wrote it for fuzz) which should be quite easy to use:
https://github.com/xeroc/delegate-slate

1) $ git clone https://github.com/xeroc/delegate-slate
2) $ cp config-example.py config.py
3) modify config.py accordingly
4) Run the script with $ python main.py

Example configuration:
Code: [Select]
## URL to RPC API of client
url = "http://10.0.0.16:19988/rpc"
## User as defined with --rpcuser=test or BitShares config file
user = 'username'
## User as defined with --rpcpassword=test or BitShares config file
passwd = 'password'
## Wallet name ( default: default :) )
wallet = "default"
## Unlock passphrase for the wallet
unlock = ""
## Delegate for which to publish a slate
delegate = "delegate.xeroc"
## Delegate which pays for the slate broadcast transaction
payee = "payouts.xeroc"
## NOTE: the private keys for both, "delegate" and "payee", must be in
## available in the wallet!
## List of trusted delegates
trusted = [
"a.delegate.charity",
"alecmenconi",
"angel.bitdelegate",
"b.delegate.charity",
"backbone.riverhead",
"bdnoble",
"bitcoiners",
"bitcube",
"bitsuperlab.gentso",
"clout-delegate1",
"crazybit"
"del.coinhoarder",
"dele-puppy",
"delegate.baozi",
"delegate.charity",
"delegate.jabbajabba",
"delegate.liondani",
"delegate.svk31",
"delegate.xeldal",
"delegate1.john-galt",
"forum.lottocharity",
"happyshares",
"luckybit",
"maqifrnswa",
"mr.agsexplorer",
"skyscraperfarms",
"spartako",
"testz",
"wackou.digitalgaia",
]

Example output:
Code: [Select]
python main.py
Opening connection to client
Opening wallet delegate
Unlocking wallet
Unapproving all previously approve delegates
Approving trusted delegates
 - a.delegate.charity
 - alecmenconi
 - angel.bitdelegate
 - b.delegate.charity
 - backbone.riverhead
 - bdnoble
 - bitcoiners
 - bitcube
 - bitsuperlab.gentso
 - bts.fordream
 - clout-delegate1
 - crazybit
 - del.coinhoarder
 - dele-puppy
 - delegate-clayop
 - delegate.baozi
 - delegate.charity
 - delegate.jabbajabba
 - delegate.liondani
 - delegate.nathanhourt.com
 - delegate.xeldal
 - delegate1.john-galt
 - dev.bitsharesblocks
 - dev0.nikolai
 - forum.lottocharity
 - happyshares
 - luckybit
 - maqifrnswa
 - marketing.methodx
 - mr.agsexplorer
 - skyscraperfarms
 - spartako
 - testz
 - titan.crazybit
 - wackou.digitalgaia
 - dev-metaexchange.monsterer
 - stan.delegate.xeldal
 - bm.payroll.riverhead
 - del0.cass
 - argentina-marketing.matt608
 - btstools.digitalgaia
 - dev.sidhujag
 - media-delegate
 - jcalfee1-developer-team.helper.liondani
 - media.bitscape
 - provisional.bitscape
 - valzav.payroll.testz
 - elmato
 - blackwavelabs
Broadcasting slate
Transactions ID: 88ed833a426d96ad93a95553e870da8eaaae7bd4

If you publish your slate please consider announcing your slate and keeping it up to date. I hope that svk eventually finds the time to list delegates slate separately and allows browsing their approvals.

Happing slating!
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline svk

Re: Howto publish a Slates for Delegates
« Reply #1 on: January 05, 2015, 03:52:14 PM »
Hey there,

I'd like to see many more (managed) slates among the elected delegates to build a web-of-trust using delegate slates such as delegate.xeroc.

Why?
The advantage of having several trusted sources of slates are:
 - users have no need to evaluate 101 delegates
 - if I trust delegate xyz .. and the delegates (how is supposedly connected to some of the other delegates) trust delegate abc, why shouldn't I?
 - assuming delegate uvy disappoints (fraud, misuse, reliability, ...) removing it from slates would directly affect all future transactions made via "as delegates recommend" - firing a delegate should be easier that way.

Helper script:
I published a script (originally wrote it for fuzz) which should be quite easy to use:
https://github.com/xeroc/delegate-slate

1) $ git clone https://github.com/xeroc/delegate-slate
2) $ cp config-example.py config.py
3) modify config.py accordingly
4) Run the script with $ python main.py

Example configuration:
Code: [Select]
## URL to RPC API of client
url = "http://10.0.0.16:19988/rpc"
## User as defined with --rpcuser=test or BitShares config file
user = 'username'
## User as defined with --rpcpassword=test or BitShares config file
passwd = 'password'
## Wallet name ( default: default :) )
wallet = "default"
## Unlock passphrase for the wallet
unlock = ""
## Delegate for which to publish a slate
delegate = "delegate.xeroc"
## Delegate which pays for the slate broadcast transaction
payee = "payouts.xeroc"
## NOTE: the private keys for both, "delegate" and "payee", must be in
## available in the wallet!
## List of trusted delegates
trusted = [
"a.delegate.charity",
"alecmenconi",
"angel.bitdelegate",
"b.delegate.charity",
"backbone.riverhead",
"bdnoble",
"bitcoiners",
"bitcube",
"bitsuperlab.gentso",
"clout-delegate1",
"crazybit"
"del.coinhoarder",
"dele-puppy",
"delegate.baozi",
"delegate.charity",
"delegate.jabbajabba",
"delegate.liondani",
"delegate.svk31",
"delegate.xeldal",
"delegate1.john-galt",
"forum.lottocharity",
"happyshares",
"luckybit",
"maqifrnswa",
"mr.agsexplorer",
"skyscraperfarms",
"spartako",
"testz",
"wackou.digitalgaia",
]

Example output:
Code: [Select]
python main.py
Opening connection to client
Opening wallet delegate
Unlocking wallet
Unapproving all previously approve delegates
Approving trusted delegates
 - a.delegate.charity
 - alecmenconi
 - angel.bitdelegate
 - b.delegate.charity
 - backbone.riverhead
 - bdnoble
 - bitcoiners
 - bitcube
 - bitsuperlab.gentso
 - bts.fordream
 - clout-delegate1
 - crazybit
 - del.coinhoarder
 - dele-puppy
 - delegate-clayop
 - delegate.baozi
 - delegate.charity
 - delegate.jabbajabba
 - delegate.liondani
 - delegate.nathanhourt.com
 - delegate.xeldal
 - delegate1.john-galt
 - dev.bitsharesblocks
 - dev0.nikolai
 - forum.lottocharity
 - happyshares
 - luckybit
 - maqifrnswa
 - marketing.methodx
 - mr.agsexplorer
 - skyscraperfarms
 - spartako
 - testz
 - titan.crazybit
 - wackou.digitalgaia
 - dev-metaexchange.monsterer
 - stan.delegate.xeldal
 - bm.payroll.riverhead
 - del0.cass
 - argentina-marketing.matt608
 - btstools.digitalgaia
 - dev.sidhujag
 - media-delegate
 - jcalfee1-developer-team.helper.liondani
 - media.bitscape
 - provisional.bitscape
 - valzav.payroll.testz
 - elmato
 - blackwavelabs
Broadcasting slate
Transactions ID: 88ed833a426d96ad93a95553e870da8eaaae7bd4

If you publish your slate please consider announcing your slate and keeping it up to date. I hope that svk eventually finds the time to list delegates slate separately and allows browsing their approvals.

Happing slating!

I'll get to it eventually I promise! You can add an issue for it on github if you'd like, that'll make sure I don't forget.
Worker: dev.bitsharesblocks

Offline CLains

  • Hero Member
  • *****
  • Posts: 2610
    • View Profile
  • BTS: clains
Re: Howto publish a Slates for Delegates
« Reply #2 on: January 06, 2015, 08:47:55 AM »
 +5%
Vote for BTS-2 witness: spectral (1.6.30)

Follow https://steemit.com/@clains

Offline wackou

Re: Howto publish a Slates for Delegates
« Reply #3 on: January 06, 2015, 09:11:17 AM »
 +5%

I also just added a publish_slate command to my bts_tools that does the same as your script, hopefully more delegates are going to publish slates if we make it as easy as possible. I am currently curating my own slate of delegates and will publish it real soon now.
Please vote for witness wackou! More info at http://digitalgaia.io

 

Google+