known:
delegate.adam
delegate1.adam
daslab
init**
delegate.charity
delegate.xeroc
do-you-even-dpos
Compiling, at 93%, will edit my post once done.
Done and done. Running 0.4.8.
Warning to delegates: it will need to re-index, leave enough time till your next block!
seed node + delegates updated.
My walled scanned for transactions.
Is this normal?
It was remarkably fast though - GJ.
Upgrade complete.
First block produced using 0.4.8: 317147
Spartako,spartako1 and spartako2 upgraded to 0.4.8
upgraded to 0.4.8 and running
even price feeds published for bitUSD ;)
liondani
liondani-delegate-1
(http://t1.gstatic.com/images?q=tbn:ANd9GcRyspH4YI-P03JAEdgihwyqTfsEkJ5enPX00TyrjCDi6SuwQNV_uQ)
PS Going to sleep know and I hope when I wake up I see Litecoin
behind us :D Good "night" bitshares team ;)
Dele-puppy is up and running on 0.4.8. My seed node is still building
0.4.8 Ready
done. I run on 0.4.8 now.
delegate.cgafeng
Updated.
"blockchain_head_block_num": 317148,
"blockchain_head_block_age": "4 seconds old",
"blockchain_head_block_timestamp": "2014-08-26T00:24:50",
"blockchain_average_delegate_participation": "93.52 %",
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "169,735.07740 BTSX",
"blockchain_delegate_pay_rate": "1.40323 BTSX",
"blockchain_share_supply": "1,999,936,650.66592 BTSX",
"blockchain_blocks_left_in_round": 93,
"blockchain_next_round_time": "at least 15 minutes in the future",
"blockchain_next_round_timestamp": "2014-08-26T00:40:20",
"blockchain_random_seed": "a3d67ecf082d8150902f1db110d58959dcab04e4",
"client_data_dir": "/home/riverhead/.BitSharesX",
"client_version": "0.4.8",
"network_num_connections": 18,
"network_num_connections_max": 100,
"ntp_time": "2014-08-26T00:24:54",
Are there instructions on how to easily upgrade to 0.4.8? I'm on Linux. I'm using the qt wallet in bitsharesx/programs/qt_wallet/bin and execute BitSharesX.
delegate1-galt upgraded to 0.4.8.
delegate1.john-galt upgraded to 0.4.8
updated:
delegate.bitsuperlab
delegate-baozi
delegate-watchman
delegates upgraded:
www.minebitshares-com
www2.minebitshares-com
compiling .. will upgrade once ready
delegate: chinese
done
btsx.chinesecommunity
updated to 0.4.8, so far so good
Updated:
delegate.xeldal
and all standbys:
delegate2.xeldal
delegate3.xeldal
bitshares-dev.invest.xeldal
seans-outpost.charity.xeldal
Updated:
boombastic
mr.agsexplorer
mrs.agsexplorer
Sent from my iPhone using Tapatalk
ok, delegates are now at 0.4.8
Active: maqifrnswa
Standby: delegate1.maqifrnswa
and the PPA is building
Did anyone else hit 2gb of ram while building? I had to add swap to my seed node to get it to compile.
compiling .. will upgrade once ready
delegate: bts.coin
Quote from: puppies on August 26, 2014, 12:42:54 AM
Did anyone else hit 2gb of ram while building? I had to add swap to my seed node to get it to compile.
I think the best way is build at your pc side, then upload to the VPS server.
I have lost 1 block when I build at the VPS server
Quote from: alt on August 26, 2014, 12:45:23 AM
Quote from: puppies on August 26, 2014, 12:42:54 AM
Did anyone else hit 2gb of ram while building? I had to add swap to my seed node to get it to compile.
I think the best way is build at your pc side, then upload to the VPS server.
I have lost 1 block when I build at the VPS server
That would work much better than compiling on all three of my servers separately. Do you just scp it, or is there a better way? and will the bitshares_client executable stand alone? If not what else do I need to copy over?
Delegates delegated-proof-of-steak and delegate.nathanhourt.com have upgraded.
Quote from: puppies on August 26, 2014, 12:46:49 AM
Quote from: alt on August 26, 2014, 12:45:23 AM
Quote from: puppies on August 26, 2014, 12:42:54 AM
Did anyone else hit 2gb of ram while building? I had to add swap to my seed node to get it to compile.
I think the best way is build at your pc side, then upload to the VPS server.
I have lost 1 block when I build at the VPS server
That would work much better than compiling on all three of my servers separately. Do you just scp it, or is there a better way? and will the bitshares_client executable stand alone? If not what else do I need to copy over?
if the machines are the same distro, it is stand alone. It might also be stand alone cross-distro, but I haven't tested it yet (I think it is, most libraries are statically linked which is sign that it might not be too dependent on system library versions)
I just scp it.
EDIT: I also have a hot standby that takes over block production while all this is going on just in case
Quote from: alt on August 26, 2014, 12:45:23 AM
Quote from: puppies on August 26, 2014, 12:42:54 AM
Did anyone else hit 2gb of ram while building? I had to add swap to my seed node to get it to compile.
I think the best way is build at your pc side, then upload to the VPS server.
I have lost 1 block when I build at the VPS server
I often build first, and then restart, but sometimes re-indexing take sometime, we need hot standby then.
cny.bts500
dac.bts500
Upgraded.
delegate.bitder updated to 0.4.8
google.helloworld
microsoft.helloworld
Upgraded
Quote from: puppies on August 26, 2014, 12:46:49 AM
Quote from: alt on August 26, 2014, 12:45:23 AM
Quote from: puppies on August 26, 2014, 12:42:54 AM
Did anyone else hit 2gb of ram while building? I had to add swap to my seed node to get it to compile.
I think the best way is build at your pc side, then upload to the VPS server.
I have lost 1 block when I build at the VPS server
That would work much better than compiling on all three of my servers separately. Do you just scp it, or is there a better way? and will the bitshares_client executable stand alone? If not what else do I need to copy over?
yes, just scp bitshares_client, my os are both ubuntu 1404
in fact, the lib which are depend is very less.
alt@alt-ThinkPad-T430s ~/workspace/bitshares_toolkit/build/programs/client $ ldd bitshares_client
linux-vdso.so.1 => (0x00007fff35154000)
libreadline.so.6 => /lib/x86_64-linux-gnu/libreadline.so.6 (0x00007f7341174000)
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f7340daf000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7340b90000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f734098c000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f7340784000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f734047f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7340179000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f733ff63000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f733fb9c000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f733f973000)
/lib64/ld-linux-x86-64.so.2 (0x00007f73413de000)
Installed 0.4.8 on Windows... when I go to Market it locks up and sits with animation as if it is updating. But then I can't do anything anymore...
x.ebit
Updated +5%
Quote from: heyD on August 26, 2014, 02:32:24 AM
cny.bts500
dac.bts500
Upgraded.
Thanks.... keep posting here and I'll vote you back in....
Quote from: happypatty on August 26, 2014, 02:35:07 AM
Installed 0.4.8 on Windows... when I go to Market it locks up and sits with animation as if it is updating. But then I can't do anything anymore...
GUI bug has been fixed in 0.4.8-a... same backend just updated GUI.
I'm updated and ready!
Quote from: DACSunlimited on August 26, 2014, 12:59:10 AM
Quote from: alt on August 26, 2014, 12:45:23 AM
Quote from: puppies on August 26, 2014, 12:42:54 AM
Did anyone else hit 2gb of ram while building? I had to add swap to my seed node to get it to compile.
I think the best way is build at your pc side, then upload to the VPS server.
I have lost 1 block when I build at the VPS server
I often build first, and then restart, but sometimes re-indexing take sometime, we need hot standby then.
I will cp -a the chain dir to a new directory, then run another client to re-index first, like:
mkdir test
cp -a delegates/chain test/
./bitshares_client --data-dir=test
after the index, close the delegate wallet, cp back the new chain directory, run delegate again.
of course, I have the backup delegate run at the same time.
toast, usd.bts500 and eur.bts500 have been upgraded to 0.4.8
now.dacwin
future.dacwin
has been upgraded to 0.4.8
Thanks.
lion
needle
nightswatch
are updated to 0.4.8
Quote from: happypatty on August 26, 2014, 02:35:07 AM
Installed 0.4.8 on Windows... when I go to Market it locks up and sits with animation as if it is updating. But then I can't do anything anymore...
Try to install the 0.4.8-a version, re-download it from bitshares-x.info
d.dacsun updated to 0.4.8
coolspeed
upgraded to 0.4.8.
upgraded and running on
delegate.taolje
Quote from: bytemaster on August 26, 2014, 02:36:41 AM
Thanks.... keep posting here and I'll vote you back in....
Quote from: yinchanggong on August 26, 2014, 02:34:29 AM
google.helloworld
microsoft.helloworld
Upgraded
We have completed the upgrade. And never missed one single block! 8)
updated
Well I somehow crashed my machine while I was rebuilding and I am totally hosed. :( :-[
I appreciate being voted out actually. It will give me a chance to restart everything from scratch. >:(
done. our team is runing on 0.4.8 now.
Delegates ID:
bts.coin
e.coin
bimin.coin
Primary delegate:
delegate.xeldal
Preferred standbys are:
delegate2.xeldal
delegate3.xeldal
If you're voting for any others like xeldal thru xeldal5 please consider my preferred standbys instead
Thanks.
all updated and producing feeds of course. v0.4.8
Quote from: bdnoble on August 26, 2014, 04:01:23 AM
Well I somehow crashed my machine while I was rebuilding and I am totally hosed. :( :-[
I appreciate being voted out actually. It will give me a chance to restart everything from scratch. >:(
I'll vote you back in when you get up.
Quote from: bytemaster on August 26, 2014, 04:21:18 AM
Quote from: bdnoble on August 26, 2014, 04:01:23 AM
Well I somehow crashed my machine while I was rebuilding and I am totally hosed. :( :-[
I appreciate being voted out actually. It will give me a chance to restart everything from scratch. >:(
I'll vote you back in when you get up.
BM, our team's following two delegates are still not generating blocks. please help to vote them back in. Thanks
e.coin
bimin.coin
Vote Coinhoarder in, please. Upgraded.
Quote from: bytemaster on August 26, 2014, 04:21:18 AM
Quote from: bdnoble on August 26, 2014, 04:01:23 AM
Well I somehow crashed my machine while I was rebuilding and I am totally hosed. :( :-[
I appreciate being voted out actually. It will give me a chance to restart everything from scratch. >:(
I'll vote you back in when you get up.
Well I don't know exactly what happened but my rig is officially dead. :'( :'( :'(
It might not ever come back. :-[ :(
Anyone interested in buying my delegate name for some BTSX? I actually have a .com and email address to go with it. :o
upgraded to 0.4.8:
ak
delegate.follow-my-vote
Early morning task :)
calabiyau & neuronics up & running. Thx for voting !
Quote from: bdnoble on August 26, 2014, 05:04:22 AM
Quote from: bytemaster on August 26, 2014, 04:21:18 AM
Quote from: bdnoble on August 26, 2014, 04:01:23 AM
Well I somehow crashed my machine while I was rebuilding and I am totally hosed. :( :-[
I appreciate being voted out actually. It will give me a chance to restart everything from scratch. >:(
I'll vote you back in when you get up.
Well I don't know exactly what happened but my rig is officially dead. :'( :'( :'(
It might not ever come back. :-[ :(
Anyone interested in buying my delegate name for some BTSX? I actually have a .com and email address to go with it. :o
Names are not transferrable.
delegate.webber
upgraded,please vote me back.
Quote from: Webber on August 26, 2014, 06:09:26 AM
delegate.webber
upgraded,please vote me back.
You promise not to produce two blocks at once?
bitcoiners
bits
upgraded to 0.4.8
vote me back in please.
upgraded forum.lottocharity
Please vote for delegate.redflag
My delegate pay rate is 50%
thank you.
wallet_approve_delegate delegate.redflag true
upgraded to 0.4.8
mr.scroodge upgraded to 0.4.8
Please vote me back in.
still crash in my windows7
please consider
voting in my standby delegate:
delegate.liondani (77% payrate)
thanks in advance :)
PS 10% will go as charity to my church in Greece (Saint Nektarios, Lavrio Kamariza, Koinotita Agiou Konstantinou. ATHENS)
will revail details ASAP.
I had some interesting discussions with several BTC miners last weekend. They control more than half of mining power in China. By saying that I have 3% of mining power in DPOS (lion needle nightswatch), I succeed to attract their attention. It is surprised that a few of them are quite interested to DPOS and be able recognize its value compared to POW.
I would like to keep on sharing my mining experience in DPOS with other crypto-community participants. It would be really appropriated if bm could kindly vote to the following delegates:
hear.me.roar.lion
fire.and.blood.dragon
my.watch.begins.nightswatch
Thank you ^^
0.4.8 updated node calabiyau still waiting to be voted back in - thank you. Takes only +5%
I have created a second delegate also.a.dele-puppy feel free to vote him in when needed and out when not. I will have him activated and ready to serve at all times.
Quote from: imwnick on August 26, 2014, 08:17:51 AM
still crash in my windows7
Quote
if you're using windows 7, right click the short cut, go to properties, click compatibility tab, then make it backwards compatible with windows xp service pack 3.
Quote from: bytemaster on August 26, 2014, 06:25:44 AM
Quote from: Webber on August 26, 2014, 06:09:26 AM
delegate.webber
upgraded,please vote me back.
You promise not to produce two blocks at once?
yes,I promise.I just forgot to close standby after upgraded to 0.4.8. :-[ :-[ sorry.
Can you vote delegate.bitder back in? It had 100% reliability for at least the last 50K blocks up to the 0.4.8 hard fork.
Thanks
doxymoron-delegate up and running 0.4.8
kokojie updated to 0.4.8
wackou-delegate upgraded to 0.4.8
Angel and Lotto delegates were updated by the time of my first post in this thread.
Sorry for not explicitly mentioning that If that is the reason for down-voting them.
EDIT:
I saw that angel-delegate has signed 2 blocks. However it wasn't running on 2 instances.
The only time it was running on 2 instances was when my wallet was opened on secondary instance and it AUTOMATICALLY entered in block production mode.
However I stopped it in timely manner and I believe it didn't produce block. (cant be 100% sure though)
Quote from: DACSunlimited on August 26, 2014, 02:59:08 PM
To All delegates:
Please do NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following
c6ce76317addf5f1b78e6700ea30da5f443f5e03 x.x 0 166 2014-08-26T14:44:10 0 N/A NO
4322211b2f74a2d43183a17042c057da64c4486c x.x 0 166 2014-08-26T14:44:10 1 N/A NO
We will strongly recommend others to vote them out.
Quote from: DACSunlimited on August 26, 2014, 03:04:13 PM
Quote from: DACSunlimited on August 26, 2014, 02:59:08 PM
To All delegates:
Please do NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following
c6ce76317addf5f1b78e6700ea30da5f443f5e03 x.x 0 166 2014-08-26T14:44:10 0 N/A NO
4322211b2f74a2d43183a17042c057da64c4486c x.x 0 166 2014-08-26T14:44:10 1 N/A NO
We will strongly recommend others to vote them out.
What's the reason is that? Sometimes when I upgrade the VPS client, I use Windows client to produce blocks temporarily, and there might be some overlap for a short while. I am wondering what's the consequence of doing that?
Quote from: ripplexiaoshan on August 26, 2014, 03:16:57 PM
What's the reason is that? Sometimes when I upgrade the VPS client, I use Windows client to produce blocks temporarily, and there might be some overlap for a short while. I am wondering what's the consequence of doing that?
You produce a fork to the network as both clients produce TWO DIFFERENT blocks at the same time and broadcast them to the network
the delegate behind you has to decide for which one to take ...
in short: forks are bad .. and should be considered harmful
updated to 0.4.8, btw it's not producing blocks
There is a bug in the fork handling code (or network code) that makes double producing blocks particularly harmful right now. Anyone caught producing 2 blocks will be voted out until we have resolved the bug.
Updated to 0.4.8 yesterday btw
Quote from: bytemaster on August 26, 2014, 05:36:25 PM
There is a bug in the fork handling code (or network code) that makes double producing blocks particularly harmful right now. Anyone caught producing 2 blocks will be voted out until we have resolved the bug.
BM .. as an advice .. you should choose your words more wisely, because in general you are (or should) not be able to just "vote someone out" .. you can just remove *your* approval votes (which for sure weight a lot and I appreciate your weight on my delegates)
However, for outsides .. this 'sounds' like you could control the delegates .. and we have a centralized security scheme ...
just my 2bitusd
happyshares-2 upgraded to 0.4.8
My delegate "mister" and "delegate.mister" has been upgraded to 0.4.8, but I hope I can replace the delegate account
mister -> sun.delegate.service
delegate.mister -> moon.delegate.service
Quote from: king on August 27, 2014, 07:19:31 AM
mister -> sun.delegate.service
delegate.mister -> moon.delegate.service
Ui ... nice name :)
Quote from: bytemaster on August 26, 2014, 02:36:41 AM
Thanks.... keep posting here and I'll vote you back in....
please vote me back
and Transfer to:
sun.delegate.service
moon.delegate.service
dc-delegate upgraded to 0.4.8
bitsharesx-delegate upgraded to 0.4.8
please vote back :P
mtang.outofcontrol upgraded to 0.4.8 :)