BitShares Forum
Main => General Discussion => Topic started by: DACSunlimited on August 20, 2014, 02:23:13 am
-
Delegates and other interested users make sure to subscribe to the delegate notification thread: https://bitsharestalk.org/index.php?topic=7067.0
This is a version for all users, provided with GUI.
All Delegates and seed nodes should upgrade their nodes to this version. The hard fork number keep unchanged.
Delegates do NOT publish price feeds until confident all delegates and users are upgraded. Publish price feed operation will officially hardfork the chain and freeze old clients.
Download and build from:
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.4
Suggestions:
1. Active Delegate, be careful and make sure you are producing blocks during upgrading.
2. There will be re-indexing.
Change Log:
- Fix market engine bug
-
Again, new market engine will be enabled on block 274000. A specific market will not start matching orders until 51 delegates have published a price feed for it.
I recommend upgraded delegates do not publish any price feeds until the community has confirmed that remaining delegates, exchanges, and seed nodes have upgraded for the hardfork.
-
When you first load the new wallet it will peg your CPU for several minutes as it reprocesses the blockchain. Do not kill it during this process.
-
A lot of Windows 7 users have this error when opening the new wallet, although it can be resolved by downloading the missing dll manually:
(http://i62.tinypic.com/2wggj1g.png)
The address to download the missing dll file:
http://62.141.41.81/releases/0029c/
Then put it in the directory of BTSX.
-
A lot of Windows 7 users have this error when opening the new wallet, although it can be resolved by downloading the missing dll manually:
(http://i62.tinypic.com/2wggj1g.png)
The address to download the missing dll file:
http://62.141.41.81/releases/0029c/
Then put it in the directory of BTSX.
This will be fixed in next version, users who have this issue can also download from this, and place it under the install path:
https://github.com/dacsunlimited/bitsharesx/raw/master/CrashRpt/bin/CrashRpt1402.dll
-
+5%
doing so right now
-
*.xeroc up-to-date
-
spartako,spartako1,spartako2 active delegates up-to-date
-
dc-delegate,bitsharesx-delegate up to date
-
After the upgrade to 4.4 the search for registered names (Directory->Registered) does not return valid results: I cannot find names that I know have been registered before the upgrade. Is it a bug or am I doing something wrong?
-
calabiyau, neuronics, navis up-to-date
-
After the upgrade to 4.4 the search for registered names (Directory->Registered) does not return valid results: I cannot find names that I know have been registered before the upgrade. Is it a bug or am I doing something wrong?
It displays well on my Windows client.
Delegates *.bts500 have been running on client 0.4.4
-
riverhead-del-server-1 up to date and producing blocks without issue.
Windows client works great after adding the .dll. Still building the Linux GUI.
Great work DACsunlimited, again!
-
Back from holidays!
betax is upto date. Needs lots of votes after a bad start, should not have long holidays ;)
-
upgraded to 0.4.4 and running smooth by now ;)
-
now.dacwin
future.dacwin
upgraded to 0.4.4 8)
-
For Ubuntu, delete the bitsharesx folder?
-
testz upgraded to 0.4.4
-
For Ubuntu, delete the bitsharesx folder?
I think, yes, instead re indexing, better to resync from beginning (for all systems).
Delete everything except wallets folder.
-
Roger!
-
windows8.1 X64 Unable to start
error:An error occurred while trying to start
-
please stop marketing engine!
I think there is a very big problem!
I'll try to write it clear
-
When you first load the new wallet it will peg your CPU for several minutes as it reprocesses the blockchain. Do not kill it during this process.
doh! this is exactly what I did!
lol recompiling.
-
please stop marketing engine!
I think there is a very big problem!
I'll try to write it clear
No delegates should publish a feed and it will be fine. What's the issue?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
windows8.1 X64 Unable to start
error:An error occurred while trying to start
Do you download CrashRpt1402.dll?
Look for instruction here: https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.4
You can also put this dll into "C:\Program Files (x86)\BitSharesX\bin" instead System32
-
please stop marketing engine!
I think there is a very big problem!
I'll try to write it clear
No delegates should publish a feed and it will be fine. What's the issue?
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Looking at the issue it is merely a thin market where he controlled the entire orderbook. A "market attack" is not something that can be prevented with software. In a live network with competitive bids/asks this attack would be harder. I would recommend that shorts maintain extra collateral early on to make the attack harder / impossible.
-
After the upgrade to 4.4 the search for registered names (Directory->Registered) does not return valid results: I cannot find names that I know have been registered before the upgrade. Is it a bug or am I doing something wrong?
It displays well on my Windows client.
Delegates *.bts500 have been running on client 0.4.4
For me is still doesn't work, neither on Mac nor on Windows 7.
E.g. if I type "sky" I only get one entry "ath3n4sky" but I am sure there is more than one registered name using the word "sky".
Can anyone confirm if you have a similar issue?
-
Is your chain fully synced?
-
delegate.bitder updated to 0.4.4
-
coolspeed
delegate upgraded to 0.4.4 already.
-
Mr.scroodge is on 0.4.4 now.
-
I haven't been posting this, but the PPA in my signature has been kept up to date within an hour of release announcements. If DACS Unlimited would like to to set up their own PPA on their own servers, or want to take over my ppa, I'd be happy to help.
-
Upgraded to 0.4.4
-
Bdnoble upgraded to 0.4.4
Sent from my iPhone using Tapatalk
-
My delegate, seed node, and personal wallet are all upgraded. I'll get my web wallet upgraded today.
-
Updated successfully . BTW, Who is running delegate commonwealth? This guy has been offline for more than one week, but BM doesn't vote it down...
-
Who is running delegate commonwealth? This guy has been offline for more than one week, but BM doesn't vote it down...
+5%
-
Who is running delegate commonwealth? This guy has been offline for more than one week, but BM doesn't vote it down...
+5%
He is gone now.
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
-
I am loving the new font color. Much easier to read on my laptop screen.
Has there been any thought (or is there already) a protected send setting? Basically allowing me to have my wallet open to look at delegates, the blockchain, etc. but when I do a transfer it requests my passphrase. I recall a lot of people had Blackcoin stolen because the wallet defaulted to completely unlocked for staking and a remote desktop vulnerability could be exploited. They have since made the default "Unlocked for staking only" requiring a password to send funds.
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
1) Install the BitSharesX client
2) Copy the .dll into the Program Files (x86)\BitShares X\bin directory
3) Launch the client.
-
Delegates:
Have you published the price feed ?
-
Delegates:
Have you published the price feed ?
Price feeds will not be published until Monday. Some last minute market manipulation attacks have caused us to tweak the parameters of the market so better protect participants.
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
1) Install the BitSharesX client
2) Copy the .dll into the Program Files (x86)\BitShares X\bin directory
3) Launch the client.
Still no change, it gives me the same error message saying that the dll is missing from the computer after I did what you instructed. I have windows 8 if that has anything to do with it.
-
Is your virus scanner eating it? I have a Win8 box around here somewhere, I'll test it out.
-
I think so, windows did block it but I ran it anyway. Then again Norton may have something to do with it. As long as I have the json file I should be ok right? Because i'm thinking about buying another computer strictly for bitshares only and start all over again.
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
Same problem here.
Tested with Win7/32 & Win7/64 machines.
Uninstalled BitsharesX on Win7/32 before install.
Overlaid BitsharesX on Win7/64.
Same error (crashrpt402dll missing) on both machines.
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
Same problem here.
Tested with Win7/32 & Win7/64 machines.
Uninstalled BitsharesX on Win7/32 before install.
Overlaid BitsharesX on Win7/64.
Same error (crashrpt402dll missing) on both machines.
Uninstall old version
Install BitSharesX 0.4.4
Place CrashRpt1402.dll into "C:\Program Files (x86)\BitSharesX\bin" at Win7/64 or "C:\Program Files\BitSharesX\bin" at Win7/32
Run the BitSharesX
Enjoy :)
-
My client (0.4.4 Windows) has been stuck at block 258808 for a few hours now and keeps cycling between "Not connected" and syncing. I've tried uninstalling and reinstalling - no dice. Any suggestions?
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
Same problem here.
Tested with Win7/32 & Win7/64 machines.
Uninstalled BitsharesX on Win7/32 before install.
Overlaid BitsharesX on Win7/64.
Same error (crashrpt402dll missing) on both machines.
Uninstall old version
Install BitSharesX 0.4.4
Place CrashRpt1402.dll into "C:\Program Files (x86)\BitSharesX\bin" at Win7/64 or "C:\Program Files\BitSharesX\bin" at Win7/32
Run the BitSharesX
Enjoy :)
I went through those steps, still got the same results. I'm just going to buy another computer and start off fresh. I've been trying to solve this problem all day. As long as I have the back up I will still have my bitshares right? Even if I don't have the client running?
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
Same problem here.
Tested with Win7/32 & Win7/64 machines.
Uninstalled BitsharesX on Win7/32 before install.
Overlaid BitsharesX on Win7/64.
Same error (crashrpt402dll missing) on both machines.
Uninstall old version
Install BitSharesX 0.4.4
Place CrashRpt1402.dll into "C:\Program Files (x86)\BitSharesX\bin" at Win7/64 or "C:\Program Files\BitSharesX\bin" at Win7/32
Run the BitSharesX
Enjoy :)
Searched both machines - only CrashRpt1402.dll file found on both HDD belongs to Keyhotee.
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
Same problem here.
Tested with Win7/32 & Win7/64 machines.
Uninstalled BitsharesX on Win7/32 before install.
Overlaid BitsharesX on Win7/64.
Same error (crashrpt402dll missing) on both machines.
You can download the .dll from DACSunlimited. There's a link in this thread somewhere.
Your folder should like this when done. Maybe even run the EXE from this folder to make sure you're running the right one.
(http://i.imgur.com/6WH5Bfk.png)
-
I upgraded last night. Everything worked fine until about 2 or 3 hours ago while I was at work.
the client wont connect. every 1-2 minutes it connects with 2 connections then stops.
The bottom of the GUI is gray and says Not Connected. I obviously have an internet connection since you are reading this. I have tried to set network parameters, nothing happened. Added nodes, nothing happened.
Re-downloaded 0.4.4 and the same thing.
Any Clues?
-
mine doesn't have exe at the end it just says bitshares x and bitshares client no .exe
-
My client (0.4.4 Windows) has been stuck at block 258808 for a few hours now and keeps cycling between "Not connected" and syncing. I've tried uninstalling and reinstalling - no dice. Any suggestions?
Same thing here. Did you get a fix?
-
I deleted my the btsx client and installed the crashrpt402dll. When I try to open the crash report its showing an error. I tried reinstalling the latest btsx wallet and it says the crashrpt402dll is missing. Now I wished I hadn't deleted my btsx wallet. Luckily I have a back up. Right now I'm just trying to get my btsx wallet up and running again with the update. Can anybody walk me through this?
Same problem here.
Tested with Win7/32 & Win7/64 machines.
Uninstalled BitsharesX on Win7/32 before install.
Overlaid BitsharesX on Win7/64.
Same error (crashrpt402dll missing) on both machines.
You can download the .dll from DACSunlimited. There's a link in this thread somewhere.
Your folder should like this when done. Maybe even run the EXE from this folder to make sure you're running the right one.
(http://i.imgur.com/6WH5Bfk.png)
This worked on both machines.
Thanks to you and testz
-
I got the client up and running, I don't know how but at the bottom it says reindexing database. is that a good sign?
-
I got the client up and running, I don't know how but at the bottom it says reindexing database. is that a good sign?
Yes, it is supposed.
-
I got the client up and running, I don't know how but at the bottom it says reindexing database. is that a good sign?
Yup!
-
now it appears to be stuck. should I just exit out and start over again or let it run its course?
-
now it appears to be stuck
Is it reindexing?
I had the problem on both machines after installing dll - uninstall and reinstall 0.4.4, uncheck run box, verify that dll is properly installed, then launch BTSX again.
-
now it appears to be stuck
Is it reindexing?
Open up the %AppData%\BitsharesX folder and sort by date. You can watch the time stamps change to know if it's working or not. The reindex takes a long time.
-
now it appears to be stuck
Is it reindexing?
Open up the %AppData%\BitsharesX folder and sort by date. You can watch the time stamps change to know if it's working or not. The reindex takes a long time.
Both of mine were stuck on different blocks while reindexing - 0.4.4 reinstall took care of it.
-
I got it up running thanks river and testz. will there be anymore updates anytime soon?
-
wait a min. now i discovered that if i simply clicked on the bitsharesx icon my wallet won't open. i have to copy and paste the dll to open my wallet is that normal?
-
wait a min. now i discovered that if i simply clicked on the bitsharesx icon my wallet won't open. i have to copy and paste the dll to open my wallet is that normal?
Basically what happened is they didn't include the .dll with the other .dll's in the install package so we have to drop it in there manually. The BitSharesX client needs it to run. So yes, this is not normal but it's what has to be done for this release.
The bleeding edge is bloody :).
-
http://bitsharesblocks.com/#/blocks and http://x.bitmeat.com/ seem to be on minority forks
-
Thanks for vote x.ebit
-
The market is right?
(http://ww4.sinaimg.cn/mw1024/e2700da8jw1ejk5nh2izmj20ub0go411.jpg)
-
I've had two crashes in the last 4 hours. First one didn't have gdb running, Second crash bt is
wallet (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
get_tail (next=<synthetic pointer>, h=0x1e0)
at /home/user/two/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
33 while( n->next_blocked_mutex ) {
(gdb) bt
#0 get_tail (next=<synthetic pointer>, h=0x1e0)
at /home/user/two/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
#1 fc::mutex::unlock (this=this@entry=0x29a4948)
at /home/user/two/bitsharesx/libraries/fc/src/thread/mutex.cpp:160
#2 0x00000000007b43f0 in ~scoped_lock (this=<synthetic pointer>,
__in_chrg=<optimized out>)
at /home/user/two/bitsharesx/libraries/fc/include/fc/thread/scoped_lock.hpp:8
#3 bts::net::detail::message_oriented_connection_impl::send_message (
this=0x29a4780, message_to_send=...)
at /home/user/two/bitsharesx/libraries/net/message_oriented_connection.cpp:195
#4 0x00000000007b4a88 in bts::net::message_oriented_connection::send_message (
this=this@entry=0x100c0108, message_to_send=...)
at /home/user/two/bitsharesx/libraries/net/message_oriented_connection.cpp:267
#5 0x00000000007aa380 in bts::net::peer_connection::send_queued_messages_task
(this=0x100c00a0)
at /home/user/two/bitsharesx/libraries/net/peer_connection.cpp:178
#6 0x00000000007aaa7c in operator() (__closure=<optimized out>)
at /home/user/two/bitsharesx/libraries/net/peer_connection.cpp:222
#7 fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::__lambda2>::run(void *, void *) (functor=<optimized out>,
---Type <return> to continue, or q <return> to quit---prQuit
Anything else needed before I close that screen?
-
anybody can help?
after
npm install
these errors occur and I can't continue making the gui for linux :(
> lineman-less@0.0.1 postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js
sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! weird error 127
npm ERR! not ok code 0
-
anybody can help?
after
npm install
these errors occur and I can't continue making the gui for linux :(
> lineman-less@0.0.1 postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js
sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! weird error 127
npm ERR! not ok code 0
ln -s /usr/bin/nodejs /usr/bin/node
-
http://bitsharesblocks.com/#/blocks and http://x.bitmeat.com/ seem to be on minority forks
I upgraded bitsharesblocks yesterday, is it on the right one now? Still on vacation here..
-
I just updated to 0.4.4
How do I get rid of the "cute" icons that appear next to my account name?
Any help would be appreciated. I do not want these robot icons.
-
What is this icon bs? http://robohash.org/ Did I download a legit client from github?
-
The icons are like a visual checksum to reduce your chances of sending funds to an incorrect account.
While the robots are cute I believe they are looking at other alternatives.
-
windows gui 0.4.4 is stucked...
"Last block was synced 32d 17h 51m 30s ago " and it goes up...
I deleted everything! (even wallet dir, appdata, all)
I put the .dll file on the right place...
8 network connections and it does not sync !!!
PS windows 7 32bit
PS2 no problems with linux server and delegates
-
Just leave it alone. It takes a LONG time and appears to be doing nothing. Just let it sit....can take hours on some hardware.
windows gui 0.4.4 is stucked...
"Last block was synced 32d 17h 51m 30s ago " and it goes up...
I deleted everything! (even wallet dir, appdata, all)
I put the .dll file on the right place...
8 network connections and it does not sync !!!
PS windows 7 32bit
PS2 no problems with linux server and delegates
-
anybody can help?
after
npm install
these errors occur and I can't continue making the gui for linux :(
> lineman-less@0.0.1 postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js
sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! weird error 127
npm ERR! not ok code 0
ln -s /usr/bin/nodejs /usr/bin/node
or install the nodejs-legacy package instead of nodejs
$ apt-get install nodejs-legacy
-
anybody can help?
after
npm install
these errors occur and I can't continue making the gui for linux :(
> lineman-less@0.0.1 postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js
sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR! weird error 127
npm ERR! not ok code 0
Sudo apt-get install nodejs-legacy
-
I've had two crashes in the last 4 hours. First one didn't have gdb running, Second crash bt is
Had a similar crash 2 days ago, and today another one kind of similar too: https://github.com/BitShares/bitshares_toolkit/issues/649
-
also, since around 0.4 or 0.4.2 (not 100% sure) my delegate seems to have a really hard time acquiring connections at the beginning. Starts with the 7-8 seed nodes it gets at the very beginning, then stays there for quite a while. Sometimes it takes off, but sometimes it just drops. Was at 3 connections just a couple of minutes ago, when I have:
(unlocked) >>> network_get_advanced_node_parameters
{
"peer_connection_retry_timeout": 30,
"desired_number_of_connections": 100,
"maximum_number_of_connections": 200
}