kimziv
Newbie
 Offline
Activity: 28
Merit: 0
|
 |
February 10, 2017, 02:01:22 AM |
|
@Eliphaz Fimk
hi, Eliphaz Fimk
I have made two redemptions of BTC (cashout) from heatwallet.com,
my heat account address is 14342346689429662556
my desired Bitcoin address is 13wUjpfu3NiAqfvcb9dCN3hmRhwRK4KW11
please handle them as soon as possible. thanks.
|
|
|
|
|
|
|
|
|
|
|
|
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
Jack Needles
Member
Offline
Activity: 94
Merit: 10
|
|
February 10, 2017, 02:02:15 AM
Last edit: February 10, 2017, 02:40:50 AM by Jack Needles |
|
stuck on 39937  Try adding the following line to conf/heat.properties: heat.enableHallmarkProtection=false
This is not a normally recommended setting, but it might help things out until HEAT gets more hallmarked nodes. Again to stress: is not normally suggested, only at this early stage. EDIT: The reasoning behind this suggestion is that there are comparatively few hallmarked nodes on the network. If any hallmarks get on a fork (especially the ones with bigger accounts), they have a very high influence on remaining nodes because those nodes "trust" the hallmarks more than everyone else. This makes it hard to follow other chains if they are held by non-hallmarked nodes, even if the forging rules declare it a stronger chain.
As far as I know, the single biggest reason for hallmark protection is to prevent Sybil attacks. This is a desirable feature of a P2P network which is why it's not typically recommended to disable. We as a community should strive to have more good hallmarked nodes on the network. But for now maybe disabling it helps to stabilize??? (not really sure) |
|
|
|
|
|
Fern
|
|
February 10, 2017, 02:20:30 AM |
|
@Eliphaz Fimk
hi, Eliphaz Fimk
I have made two redemptions of BTC (cashout) from heatwallet.com,
my heat account address is 14342346689429662556
my desired Bitcoin address is 13wUjpfu3NiAqfvcb9dCN3hmRhwRK4KW11
please handle them as soon as possible. thanks.
Over 24 hours? These guys have to sleep. It will happen, hang in there |
|
|
|
|
Stumpsty
Member
Offline
Activity: 105
Merit: 11
|
|
February 10, 2017, 02:33:25 AM |
|
New wallet is really cool good job!
|
|
|
|
|
Stumpsty
Member
Offline
Activity: 105
Merit: 11
|
|
February 10, 2017, 02:42:19 AM |
|
New wallet is really cool good job!
But is it safe to mine? |
|
|
|
|
|
peggy2jj
|
|
February 10, 2017, 02:43:06 AM |
|
stuck on 39937 same here |
|
|
|
|
|
lurker10
|
|
February 10, 2017, 06:58:19 AM |
|
Where are we at?
my node 0.9.6 is on block 40429 after syncing from scratch.
heatwallet.com block 40365
heatbrowser.com latest 41326
|
|
|
|
|
Crapsy
|
|
February 10, 2017, 07:05:27 AM |
|
We are all waiting for verymuchso to wake up to a glorious day of massive coding  I don't see any workarounds to get to connect the proper way at the moment. |
|
|
|
|
u15776
Newbie
Offline
Activity: 27
Merit: 0
|
|
February 10, 2017, 09:52:04 AM |
|
Version 0.9.6
Connect to localhost:
2017-02-10 10:47:17 INFO Initializing unconfirmed transactions
2017-02-10 10:47:17 INFO To complete storage recovery process please restart
2017-02-10 10:47:17 INFO Shutting down HEAT server 0.9.6
2017-02-10 10:47:17 INFO HEAT server 0.9.6 stopped.
"Shutdown hook triggered, initiating HEAT 0.9.6 shutdown"
"[SPAWN EXIT] spawn bin\\heatledger.bat ENOENT"
Connect to remotehost:
"Fatal error: java.lang.OutOfMemoryError: Ran out of virtual memory on a 32-bit JVM, either use a 64-bit JVM or *reduce* your heap size"
"Shutdown hook triggered, initiating HEAT 0.9.6 shutdown"
"[SPAWN] DONE!"
Any advise? Thanks.
|
|
|
|
|
|
Crapsy
|
|
February 10, 2017, 10:11:23 AM |
|
At the moment a clean restart works. Many have successfully joined the chain with a clean local wallet.
|
|
|
|
|
Jiddu
Sr. Member
Offline
Activity: 390
Merit: 250
into the clusterfuck
|
|
February 10, 2017, 10:18:44 AM |
|
Any advise? Thanks.
Yes: Version 0.9.6
Connect to localhost:
2017-02-10 10:47:17 INFO Initializing unconfirmed transactions
2017-02-10 10:47:17 INFO To complete storage recovery process please restart
2017-02-10 10:47:17 INFO Shutting down HEAT server 0.9.6
2017-02-10 10:47:17 INFO HEAT server 0.9.6 stopped.
"Shutdown hook triggered, initiating HEAT 0.9.6 shutdown"
"[SPAWN EXIT] spawn bin\\heatledger.bat ENOENT"
Connect to remotehost:
"Fatal error: java.lang.OutOfMemoryError: Ran out of virtual memory on a 32-bit JVM, either use a 64-bit JVM or *reduce* your heap size"
"Shutdown hook triggered, initiating HEAT 0.9.6 shutdown"
"[SPAWN] DONE!"
Any advise? Thanks.
|
|
|
|
|
u15776
Newbie
Offline
Activity: 27
Merit: 0
|
|
February 10, 2017, 10:45:42 AM |
|
Any advise? Thanks.
Yes: Version 0.9.6
Connect to localhost:
2017-02-10 10:47:17 INFO Initializing unconfirmed transactions
2017-02-10 10:47:17 INFO To complete storage recovery process please restart
2017-02-10 10:47:17 INFO Shutting down HEAT server 0.9.6
2017-02-10 10:47:17 INFO HEAT server 0.9.6 stopped.
"Shutdown hook triggered, initiating HEAT 0.9.6 shutdown"
"[SPAWN EXIT] spawn bin\\heatledger.bat ENOENT"
Connect to remotehost:
"Fatal error: java.lang.OutOfMemoryError: Ran out of virtual memory on a 32-bit JVM, either use a 64-bit JVM or *reduce* your heap size"
"Shutdown hook triggered, initiating HEAT 0.9.6 shutdown"
"[SPAWN] DONE!"
Any advise? Thanks.
Restarted many times. For a non-software engineer  : do I have to download something from Java? |
|
|
|
|
|
|
Jiddu
Sr. Member
Offline
Activity: 390
Merit: 250
into the clusterfuck
|
|
February 10, 2017, 11:22:08 AM |
|
@u15776 Did you get the same message after restarting? However, there are still issues with 0.9.6. What you can try for now is to delete the blockchain dir, put this into your conf\heat.properties file and start again: heat.wellKnownPeers=78.46.99.11;192.3.156.15;163.172.163.4
heat.enableHallmarkProtection=false And better uninstall 32bit Java before installing 64bit. |
|
|
|
|
u15776
Newbie
Offline
Activity: 27
Merit: 0
|
|
February 10, 2017, 11:31:10 AM |
|
|
|
|
|
|
Stumpsty
Member
Offline
Activity: 105
Merit: 11
|
|
February 10, 2017, 01:28:48 PM |
|
|
|
|
|
|
kimziv
Newbie
Offline
Activity: 28
Merit: 0
|
 |
February 10, 2017, 02:10:29 PM |
|
https://i.imgsafe.org/dca083da4a.png@Eliphaz Fimk hi, Eliphaz Fimk I have made two redemptions of BTC (cashout) from heatwallet.com, my heat account address is 14342346689429662556 my desired Bitcoin address is 13wUjpfu3NiAqfvcb9dCN3hmRhwRK4KW11 please handle them as soon as possible. thanks.
|
|
|
|
|
halibit
Legendary
Offline
Activity: 1596
Merit: 1006
|
|
February 10, 2017, 05:11:50 PM |
|
Will do that but later. Wallet have mining on different forks and cant release any extra coins till im sure there is no roll back or fork. Currently wallet is in fork but will try to get right chain when im on office. Not most easy wallet I think. Is exchange feature reason for so many forks or what? just curious question.. |
|
|
|
|
ohweoh
Newbie
Offline
Activity: 34
Merit: 0
|
|
February 10, 2017, 05:36:03 PM |
|
What's going on with the ccex issue?
Svante stated he was working with them last night.
What's the update?
|
|
|
|
|
|
StewieG
|
|
February 10, 2017, 05:55:42 PM |
|
The fucking A2A exchange is totally broken! Is anything working here??!?!!?? It says I have now only 0.3btc, yesterday I had 0.4btc. Also I am missing about 14k Heat? WHAT IS THIS SHIT! This heat bullsit is pissing me off so hard! I JUST WANTED TO GET RID OF THIS BULLSHIT AND NOT EVEN THIS WORKS!!!! EVERYTHING IS FUCKED! I know how this guy feels https://www.youtube.com/watch?v=s9Bg4UU76so |
|
|
|
|
|
