Author Topic: [DNS] v0.0.2 - Trade the snapshot and fight for delegate pay  (Read 43824 times)

0 Members and 1 Guest are viewing this topic.

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
Compiling fails on my vps server running Ubuntu 14.04

Code: [Select]
[ 65%] Generating genesis_json.cpp
[ 65%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 4
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
make: *** [all] Error 2

>>> approve bitcoiners

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
Any dotp2p_bid and dotp2p_buy commands return "This operation is not enabled yet."
Is this expected?
UPDATE: hmm after reading more carefully the thread I got the answer -> Yes it is expected.

Offline svk

+5% :D

I voted emski angel-delegate

Thanks!


On the testing site:
I've experienced this issue: https://github.com/BitShares/bitshares_toolkit/issues/794 .
The workaround (deleting node config) worked so I assume it is not merged.

Yea I experienced this also when upgrading my delegate from v0.0.1 to v0.0.2. With two clients running the new client would fail to sync, upon closing the old client then restarting the new one I immediately got synced up. Was the exact same behaviour I was seeing before issue 794 got fixed.
Worker: dev.bitsharesblocks

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
+5% :D

I voted emski angel-delegate

Thanks!


On the testing site:
I've experienced this issue: https://github.com/BitShares/bitshares_toolkit/issues/794 .
The workaround (deleting node config) worked so I assume it is not merged.

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Can someone send 1 DNS to bitcube?

Thank you.
« Last Edit: October 03, 2014, 03:26:37 pm by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1905
    • View Profile
  • BitShares: ebit
« Last Edit: October 03, 2014, 01:30:36 pm by ebit »
telegram:ebit521
https://weibo.com/ebiter

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I've started a seed node for keyID:
46.10.205.0:42124

I've added also some 1% delegates:
angel-delegate
immortal
emski

I'll do some experiments later today.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
I might find a bug. Pay rate cannot be changed.

That is not a bug. Pay can be lowered but not raised. If you're at 0% and want to be 1% you need to create a new delegate. It works this way in BitSharesX as well.

It is. I tried to decrease pay rate but did not work in GUI.
Do you know how to do this in CLI?

Interesting. From the CLI check out wallet_account_update_registration, the last parameter is delegate_pay_rate.

CLI works. GUI obviously has a bug. Thank!

I had the same problem.
The gui tries to register the account again instead of updating it....
It worked for me also only on cli with the command "update_registration" (instead of register_account)

Offline Riverhead

Are DNS keys deterministic like in BitSharesX? I'm assuming so since it's using the same toolkit but just want to be sure so I can plan my backup strategy.

Offline svk

I'm so excited that I have the first delegate in Korea!  ;D

Code: [Select]
wallet_approve_delegate delegate-clayop true

You should reduce your payrate though, this is using the inflation based delegate pay model, so 100% is unacceptable. 1% is what everyone else is using, it gives about 10DNS per block.

ebit team in live
ebit1 pay-rate 1%
rose1 pay-rate 10%
ebit2 pay-rate 1%

Code: [Select]
wallet_account_set_approval ebit1 true
wallet_account_set_approval rose1 true
wallet_account_set_approval ebit2 true

Same for you, 10% is a very high payrate, what are you doing that would justify it?

1% is NOT what EVERYONE else is doing.  Based on Toast post my understanding was that most everyone would use 0% and only those who were actively working with him to build it would get 1%.

Maybe TOAST can clarify.

You are of course correct, I meant everyone else as in the ones actually charging a fee and getting voted in.
Worker: dev.bitsharesblocks

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1905
    • View Profile
  • BitShares: ebit
I'm so excited that I have the first delegate in Korea!  ;D

Code: [Select]
wallet_approve_delegate delegate-clayop true

You should reduce your payrate though, this is using the inflation based delegate pay model, so 100% is unacceptable. 1% is what everyone else is using, it gives about 10DNS per block.

ebit team in live
ebit1 pay-rate 1%
rose1 pay-rate 10%
ebit2 pay-rate 1%

Code: [Select]
wallet_account_set_approval ebit1 true
wallet_account_set_approval rose1 true
wallet_account_set_approval ebit2 true

Same for you, 10% is a very high payrate, what are you doing that would justify it?

It's a pity that be burned.
telegram:ebit521
https://weibo.com/ebiter

Offline GaltReport

I'm so excited that I have the first delegate in Korea!  ;D

Code: [Select]
wallet_approve_delegate delegate-clayop true

You should reduce your payrate though, this is using the inflation based delegate pay model, so 100% is unacceptable. 1% is what everyone else is using, it gives about 10DNS per block.

ebit team in live
ebit1 pay-rate 1%
rose1 pay-rate 10%
ebit2 pay-rate 1%

Code: [Select]
wallet_account_set_approval ebit1 true
wallet_account_set_approval rose1 true
wallet_account_set_approval ebit2 true

Same for you, 10% is a very high payrate, what are you doing that would justify it?

1% is NOT what EVERYONE else is doing.  Based on Toast post my understanding was that most everyone would use 0% and only those who were actively working with him to build it would get 1%.

Maybe TOAST can clarify.


Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
I might find a bug. Pay rate cannot be changed.

That is not a bug. Pay can be lowered but not raised. If you're at 0% and want to be 1% you need to create a new delegate. It works this way in BitSharesX as well.

It is. I tried to decrease pay rate but did not work in GUI.
Do you know how to do this in CLI?

Interesting. From the CLI check out wallet_account_update_registration, the last parameter is delegate_pay_rate.

CLI works. GUI obviously has a bug. Thank!
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline Riverhead

I might find a bug. Pay rate cannot be changed.

That is not a bug. Pay can be lowered but not raised. If you're at 0% and want to be 1% you need to create a new delegate. It works this way in BitSharesX as well.

It is. I tried to decrease pay rate but did not work in GUI.
Do you know how to do this in CLI?

Interesting. From the CLI check out wallet_account_update_registration, the last parameter is delegate_pay_rate.

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
I might find a bug. Pay rate cannot be changed.

That is not a bug. Pay can be lowered but not raised. If you're at 0% and want to be 1% you need to create a new delegate. It works this way in BitSharesX as well.

It is. I tried to decrease pay rate but did not work in GUI.
Do you know how to do this in CLI?
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop