Show Posts
|
Pages: [1] 2 3 »
|
You could always go look at the financials posted for YE2014 to see what the cash situation was like. ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) Where is the link for it?
|
|
|
I don't know how ActiveMining is going on, so can you get back our investment?
|
|
|
I want to do some testing tomorrow with more than half a dozen servers any chance of getting at least a dozen running?
Is there any full document for the users to have a node up and help test? I found that so many nodes set up guides, scripts and threads in last December so as to prevent DDoS to Nxt. BTW, why not buy nodes for the users to set up those servers with the working fund of SuperNET. If the document is ready and the nodes fee can be covered by SuperNET, there will be most probably more and more users taking party in the test.
|
|
|
Well that's good to hear that there's still development. I'll definitely check out the Mirth client. Did you download the blockchain separately that is alot faster. The blockchain is being pruned right now. Soon you will get up and running within 5 minutes. If you'd like to download the blockchain http://huntercoin.info/help/installGreat news. Can't wait for it.
|
|
|
just found a bug that possibly is related to your issues: If someone initiated more than one transfer within the same block then only one of them will be displayed in the blockexplorer search and - that is more important - the calculation of an addresses' balance will be wrong then as well [=counting in only one tx per block](!). We target V0.59 with minor improvements and bug fixes to be available shortly in around 24h. So I guess in your case, Fonzarelli, your local client accepts the transfer since balance is OK, but the net does not accept it since calculation of that addresses' balance is not right. You should be able to send a value <=10789.6 EXO but nothing more. Sorry for the inconveniences but I am glad to found this bug so fast. Repost - Potential Bug
OK... the transaction I sent from EXOdfsN5u5WPB4BNsswrdp21tkuyE3mWHpCmdbme to EXOdfsN5u5WPB4BNsswrdp21tkuyE3mWHpCmdbme for 5555.55 EXO appears in my transactions but NOT under the transactions when you put the recipient's address in the Block Explorer.
That's the same issue. Bug fix is easy (simply use continue instead of break in 3 lines) and will surely be available in 0.59#edit: partially wrong.. only targetAddress has been calculated wrongly - sender's addresses always calculated correctly regards eXocoin #edit: Solved in v0.59 (release tomorrow). Your 5555.55 appears now on both sides andFonzarelli's balance calculated to a sum of 20122.9 EXO - so this was not an issue within the chain itselfI generated 3 * 10000 coins and then sent 3 * 8888.88 coins out in several minutes, and I think those operations in one block.
|
|
|
please send me some test EXOs. will send them back with simple interest of 100% ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) EXOyahgZ5Csz31ctmnK22arfAUUWAaZRs1gxdbhd After I sent 8888.88 EXO to chinnuperiya. I got 1000 EXO interest from him. Thank you!
|
|
|
Looking forward to test the new version! ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) An advice from an old c++ coder: bugfix: double-round function was not accurate enough for one comparision
Don't use floating point in a financial application! Nasty round and compare bugs ahead! ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) Use a long or longlong and do integer division to get to the decimals. Yes that might be a good idea;-) Right now it will round it to 12 decimals accuracy and is working as well.... but we will consider changing that. Make that priority, please. Before the release date. Floating points should not be used in financial applications. +1 Make it priority! Only integer in finance. BTW, anyone with address in the recent posts will get 8888.88 exo.
|
|
|
I can sell 1 BTC stake for 81 BTC. If interested, please PM me and let's do the deal with Anon136's escrow service and I can pay the escrow fee.
The above quotation is valid in 3 days, and I may change it after that.
|
|
|
I generated 10000 coins this morning, and now the network connection is 4, a little less than this morning. I sent 12.34567 coins out to the above address.
|
|
|
sent 0.03BTC to 1NfVZ4fHcBLCk6932b7ZVyPQ8wNDQ5NGCu txid: 620936666dd2259a90ed37a959e2c9cb3fcd75e808f1a0f7d6eaa9eb39f435ff NXTL: 5396980722153068858
|
|
|
I assume you are using bitcoin qt. If you are not, please tell me which wallet you are using, and ignore the following. To re-broadcast your tx, first get the raw transaction. Open bitcoin-qt, click "Help, then click "Debug window" and click "Console". Enter "getrawtransaction <your tx id>" (without the " and <>) Copy the long strings and enter it on http://blockchain.info/pushtxThanks for your help. Yes, I'm using bitcoin-qt. Can I delete this tx if I don't want to rebroadcast and send it. I can't make sure whether the exchange can get the coin because I have generated a new address in the exchange platform.
|
|
|
Have you checked the tx on blockchain.info or blockr.io?
If your tx is not found or is shown unconfirmed on the sites, then a -rescan would not help at all, not because your wallet is encrypted.
The tx can't be found on both blockchain.info and blockr.io.
|
|
|
Hi, I performed a sending tx out when the blockchain data lags 5 days, and the tx was broadcasted only through 3 nodes. It was always through 3 nodes after a long period of time, so I closed bitcoin wallet and then restarted it. However, the tx is always 0 confirmed though the blockchain data is to date and the bitcoin-qt is started with "-rescan". I'm now wondering the "-rescan" didn't take effect because the wallet is encrypted. So how should I do to rebroadcast or delete the tx?
Thanks.
|
|
|
ATC 1.5 BTC 6d4ff8423882796e03b380cad1ff74d6ddf11561f409576761588660311dcfbf allwelder 0.28 BTC e37b4855e800fbceeec94a4b71b43873ed9d2dbe0e2b040cc3dcecec3278659f evoked22 0.99 BTC 1c1e4145d07a935b02f30fa1aba288ba4afe914f109b4069f4a920a0892e109b
Thank you Anon136!
|
|
|
Sent 1.515 BTC (1.5 BTC + 0.015 BTC fee) to Anon136 for escrow. txid: 6d4ff8423882796e03b380cad1ff74d6ddf11561f409576761588660311dcfbf
Anon136, Please confirm it.
|
|
|
|