Search content
Sort by
Showing 20 of 84 results by mark613
Re: C-CEX.com Trusted, Secure & Friendly Exchange Since 2013. 100+ Alts,USD,Low Fees
How many days is the 1337 wallet going to be in maintenance? It's been down for a while now.
I'ts already fixed. Thanks to 1337 dev who was online with us to help with 1337 wallet sync issue.
Awesome man thanks
Is Amagi Metals still active?
Seeing how they haven't responded in nearly a month should be the only answer you need. Reputable companies like Silver dot com , Provident Metals and JM Bullion now taking bitcoin makes ordering your precious metals worry free.
Re: ◆Rubies◆ [RBIES] Bet-Mining & PoS | Multi-Business backed currency Proof of Use.
NEW PROMO from CryptoJacks team for RUBIES Coin
CRYPTOJACK JUNE MADNESS
Wager 5000 Rubies and claim 1 Rubies every day in JUNE @ http://cryptojacks.com/rubies
Team will be Creating a Spread Sheet and will be making Daily payouts for each users.
Users can claim the same at any point of time after which their details will be updated in Excel every day
The Current promo is only for JUNE Month
Alternatively users can claim faucet Payouts / Giveaway of .05 Rubies every 15 Minutes !
Note : I am Posting for them till Cryptojack Team Creates a New Ann
CRYPTOJACK JUNE MADNESS
Wager 5000 Rubies and claim 1 Rubies every day in JUNE @ http://cryptojacks.com/rubies
Team will be Creating a Spread Sheet and will be making Daily payouts for each users.
Users can claim the same at any point of time after which their details will be updated in Excel every day
The Current promo is only for JUNE Month
Alternatively users can claim faucet Payouts / Giveaway of .05 Rubies every 15 Minutes !
Note : I am Posting for them till Cryptojack Team Creates a New Ann
would you be so kind to link me to the rules and HE of the BJ? I could not find it
thx
Rules will be updated slowly for each coin they make
If you go for the lowest possible , you can give an edge of around 0.3% to the player (negative house edge) , and the highest possible is around 2.47% house edge.
The most significant option is the 3:2 or 6:5 blackjack payout.
The 6:5 blackjack payout significantly reduces house edge
Cryptojack offers 6:5 Blackjack payout atm
A 6:5 blackjack most definitely doesn't reduce the house edge.
Re: Amagi Metals is back under new ownership - Bitcoin payment option available
You guys lost a lot of business because of unfilled orders, literally NO customer service and basically keeping everyone in the dark on what was going on these last several months. It would have been so easy to keep customers simply by telling us what was going on. Instead, there was nothing but silence and denial from your Reddit thread how Anthem wasn't buying out/acquiring Amagi Metals. It's a shame too because at one time Amagi Metals was actually a shining star in the Bitcoin community.
Signed,
A former customer
Signed,
A former customer
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
2. after looking at this again I was incorrect on what is happening. In version 9.1.60 when you mined a block you would have 4 transactions. The first transaction was labeled "mined" with the pickaxe and the amount of the block (currently 45). The second transaction was a "deposit" for the block. The third transaction was a "deposit" from my prepared deposit. The fourth transaction was labeled "deposit change" with any overage from my prepared deposit coming back to me. In 9.1.74 I am no longer getting that first transaction labeled "mined" with the pickaxe and the value of the block mined.
I must say that you have a firm grip on how the system works, I'm impressed!
Just one small correction to make things maybe even more clear:
The deposit change can only come from the deposit tx that the system creates by itself, and that deposit tx is only created to spend the reward. The deposit txs that you prepare manually yourself can never be modified, and hence can not have a deposit change. As mentioned, just a minor clarification.
However... I'm working on having the software automatically prepare deposits from everything that is available in a wallet to simplify the mining process. That way a miner could just start the miner, set some parameters, and watch the wallet content go into deposit block by block. I didn't want to enable this before, since software automated access to a wallet always poses a risk. But I think the time is right to introduce it now, with a switch to be able to disable it.
Ah ok I was close
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
I'm having crashing issues on 9.1.74 running in -server mode. Any time I try to send a transaction i get a fatal error that closes down the program. I have no problem sending transactions when not in -server mode. I now occasionally get this error in regular mode as well. I am using the Windows 64 bit program in Win 7. Also, when solving a block it no longer says "Mined" under the type column in the transaction. It just says deposit. The pickaxe is now gone as well. Just cosmetic but letting ya know.
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
The debug output that you added at the end of the message, is that the miner shutting down after a while?
Am I correct when I say that there are three errors here:
1. Not possible to send txs in server mode?
2. The mined column wrong (minor error)?
3. The miner (the whole wallet?) dying on this line: miner.cpp.Line 1021?
This windows popup is the initial thing that happens when I try to send a transaction. Gives me 3 buttons (retry, ignore, and abort). Hitting the "retry" button brings up another window titled Microsoft Visual C++ runtime library. The messege in that window reads as follows:
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
the "abort" button shuts down and closes the program. If I hit the ignore key a few times (2-5 on average) the popup eventually goes away and I can send the transaction without kicking me out of the wallet.
1. Intermittently can't send a transaction. I should mention these are internal transaction where I am sending small amounts 5-6 cre to my personal receiving addresses to make prepared deposits.
2. after looking at this again I was incorrect on what is happening. In version 9.1.60 when you mined a block you would have 4 transactions. The first transaction was labeled "mined" with the pickaxe and the amount of the block (currently 45). The second transaction was a "deposit" for the block. The third transaction was a "deposit" from my prepared deposit. The fourth transaction was labeled "deposit change" with any overage from my prepared deposit coming back to me. In 9.1.74 I am no longer getting that first transaction labeled "mined" with the pickaxe and the value of the block mined.
3. Yes, the wallet shuts down.
Aha ok. Are you by any chance running your miner with a locked (encrypted) credits_wallet.dat file? That would explain the part that you can not view the mined coinbase tx in your transaction history. The reason is as follows:
- If you have an unencrypted credits_wallet.dat file, then the mining software automatically and directly will spend the coinbase tx with the deposit tx if you are including the reward as deposit. You normally do this. If the credits_wallet.dat file is encrypted, this can not be done (the software does not have "spending access" to the coinbase tx output, it can not use the key, only view it). To get around this problem, the coinbase tx output spending key is instead stored into the deposit_wallet.dat file, where the software always can use it; the deposit_wallet.dat file is never encrypted. Since the coinbase output is spent directly, the coinbase output key is really just a "throw away key" and the reward from the coinbase ends up in the deposit tx. The key for the coinbase tx are however still hanging around in the deposit_wallet.dat file. BUT, when they are stored there, the transaction history extracted from the credits_wallet.dat file does not cointain the coinbase tx output key, and therefore does not show the coinbase tx. This could of course be remedied by merging the transaction history of the credits_wallet.dat and the deposit_wallet.dat files into one. This has not been done yet due to technical complexity and lack of time.
One other explanation, the deposit_wallet.dat file is ONLY used for temporary storage of prepared but not yet block included deposit txs. Except for the usage described above. It is NOT related to deposit txs in any other way. Deposit txs, like any other txs, lives in the blocks and the related keys for your own deposit txs lives in your credits_wallet.dat file. To repeat this; the deposit_wallet.dat file is ONLY a temporary working file, containing prepared but not yet used deposits, and as described above, "throw away" one time keys, used for coinbase txs that are spent by deposits txs when the coinbase tx output key can not be stored in credits_wallet.dat. That happens when credits_wallet.dat is encrypted. The deposit_wallet.dat can however be useful to save at the same time as backups of the other wallet files are done since it contains uniquely generated keys, and keys should in principle never be thrown away.
This makes me believe that a single backup option that backups all three wallets at the same time probably should be added.
Good to hear that you have found a way (mostly) around the error popup.
I'm working on simulating the problems that you are having, however, so far, haven't been able to reproduce them.
Maybe I should take this discussion in a PM and then just post the outcome here?
Yes my credits_wallet.dat is encrypted. Come to think of it, I don't think I started having problems with these errors until after I encrypted my wallet.
My crystal ball says you will be able to replicate the problem once you encrypt the credits_wallet.dat
Yeah we can take this to PM's so peeps don't have to wade through all of this any longer
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
I'm having crashing issues on 9.1.74 running in -server mode. Any time I try to send a transaction i get a fatal error that closes down the program. I have no problem sending transactions when not in -server mode. I now occasionally get this error in regular mode as well. I am using the Windows 64 bit program in Win 7. Also, when solving a block it no longer says "Mined" under the type column in the transaction. It just says deposit. The pickaxe is now gone as well. Just cosmetic but letting ya know.
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
The debug output that you added at the end of the message, is that the miner shutting down after a while?
Am I correct when I say that there are three errors here:
1. Not possible to send txs in server mode?
2. The mined column wrong (minor error)?
3. The miner (the whole wallet?) dying on this line: miner.cpp.Line 1021?
This windows popup is the initial thing that happens when I try to send a transaction. Gives me 3 buttons (retry, ignore, and abort). Hitting the "retry" button brings up another window titled Microsoft Visual C++ runtime library. The messege in that window reads as follows:
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
the "abort" button shuts down and closes the program. If I hit the ignore key a few times (2-5 on average) the popup eventually goes away and I can send the transaction without kicking me out of the wallet.
1. Intermittently can't send a transaction. I should mention these are internal transaction where I am sending small amounts 5-6 cre to my personal receiving addresses to make prepared deposits.
2. after looking at this again I was incorrect on what is happening. In version 9.1.60 when you mined a block you would have 4 transactions. The first transaction was labeled "mined" with the pickaxe and the amount of the block (currently 45). The second transaction was a "deposit" for the block. The third transaction was a "deposit" from my prepared deposit. The fourth transaction was labeled "deposit change" with any overage from my prepared deposit coming back to me. In 9.1.74 I am no longer getting that first transaction labeled "mined" with the pickaxe and the value of the block mined.
3. Yes, the wallet shuts down.
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
I'm having crashing issues on 9.1.74 running in -server mode. Any time I try to send a transaction i get a fatal error that closes down the program. I have no problem sending transactions when not in -server mode. I now occasionally get this error in regular mode as well. I am using the Windows 64 bit program in Win 7. Also, when solving a block it no longer says "Mined" under the type column in the transaction. It just says deposit. The pickaxe is now gone as well. Just cosmetic but letting ya know.
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Thanks for a good error report. Did you use the provided torrent or synced from scratch?
Will look into this straight away.
I synced from 9.1.73. The strange thing is I also started getting this error on 9.1.60 shortly after 9.1.74 was released. Not sure if there is any connection or not. My 9.1.60 version was synced from torrent.
The 0.9.1.60 working directory and 0.9.1.74 working directory are unfortunately incompatible. So if you are trying to run the two versions against the same working directory, they may overwrite each other. Are you doing that or do you have two different working dirs?
I was running two separate directories so nothing was mixing.
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
I'm having crashing issues on 9.1.74 running in -server mode. Any time I try to send a transaction i get a fatal error that closes down the program. I have no problem sending transactions when not in -server mode. I now occasionally get this error in regular mode as well. I am using the Windows 64 bit program in Win 7. Also, when solving a block it no longer says "Mined" under the type column in the transaction. It just says deposit. The pickaxe is now gone as well. Just cosmetic but letting ya know.
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Thanks for a good error report. Did you use the provided torrent or synced from scratch?
Will look into this straight away.
I synced from 9.1.73. The strange thing is I also started getting this error on 9.1.60 shortly after 9.1.74 was released. Not sure if there is any connection or not. My 9.1.60 version was synced from torrent.
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
I'm having crashing issues on 9.1.74 running in -server mode. Any time I try to send a transaction i get a fatal error that closes down the program. I have no problem sending transactions when not in -server mode. I now occasionally get this error in regular mode as well. I am using the Windows 64 bit program in Win 7. Also, when solving a block it no longer says "Mined" under the type column in the transaction. It just says deposit. The pickaxe is now gone as well. Just cosmetic but letting ya know.
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Debug output:
2015-09-09 02:17:24 ERROR: deposit transaction could not sign coinbase
2015-09-09 02:17:24
ERROR! IncrementExtraNonce() : Failed to recalculate coinbase as deposit. Miner exiting.
I'm also getting a popup window titled "MinGW Runtime -Assertion"
Inside the window says: File: miner.cpp.Line 1021
Expression: false
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
Have a quick question on prepared deposits. Why does it take 101 confirmations to get the extra change back?
It's not a big deal I was just curious.
It's not a big deal I was just curious.
Re: CREDITS [CRE] | SHA256 | SIDECHAIN | NEW BLOCK-DEPOSIT FEATURE | OFFICIAL THREAD
Hey guys,
I'm having problems with the torrent file "credits-win-2015-06-03.torrent" that is suppose to help sync the QT wallet a little faster.
Getting a failed to read block error. Just passing along the info.
Oh, this is on the 9.1.73 beta version win 64 bit
2015-09-05 09:16:33 Bitcoin: Trimming file blk00236.dat...
2015-09-05 09:16:33 *** Failed to read block info
2015-09-05 09:16:48 ERROR: Bitcoin: Bitcoin_WriteBlockCompressedToDisk() : FindCompressedPos failed
2015-09-05 09:16:48 *** Bitcoin: Failed to write block compressed data
2015-09-05 09:16:49 Requesting shutdown
2015-09-05 09:16:49 ERROR: Bitcoin: ConnectTip() : Could not compress block history!
2015-09-05 09:16:49 ERROR: Bitcoin: ConnectTip() : Could not trim block history!
2015-09-05 09:16:49 ERROR: Bitcoin: AcceptBlock() : ReceivedBlockTransactions failed
2015-09-05 09:16:49 ERROR: Bitcoin: ProcessBlock() : AcceptBlock FAILED
2015-09-05 09:16:49 ERROR: Bitcoin: AcceptToMemoryPool : nonstandard transaction: non-final
2015-09-05 09:16:49 Running Shutdown in thread
I'm having problems with the torrent file "credits-win-2015-06-03.torrent" that is suppose to help sync the QT wallet a little faster.
Getting a failed to read block error. Just passing along the info.
Oh, this is on the 9.1.73 beta version win 64 bit
2015-09-05 09:16:33 Bitcoin: Trimming file blk00236.dat...
2015-09-05 09:16:33 *** Failed to read block info
2015-09-05 09:16:48 ERROR: Bitcoin: Bitcoin_WriteBlockCompressedToDisk() : FindCompressedPos failed
2015-09-05 09:16:48 *** Bitcoin: Failed to write block compressed data
2015-09-05 09:16:49 Requesting shutdown
2015-09-05 09:16:49 ERROR: Bitcoin: ConnectTip() : Could not compress block history!
2015-09-05 09:16:49 ERROR: Bitcoin: ConnectTip() : Could not trim block history!
2015-09-05 09:16:49 ERROR: Bitcoin: AcceptBlock() : ReceivedBlockTransactions failed
2015-09-05 09:16:49 ERROR: Bitcoin: ProcessBlock() : AcceptBlock FAILED
2015-09-05 09:16:49 ERROR: Bitcoin: AcceptToMemoryPool : nonstandard transaction: non-final
2015-09-05 09:16:49 Running Shutdown in thread
Amagi Metals has gone AWOL so I would definitely not recommend them. They aren't accepting bitcoins for payment anyway and haven't for months. Their presence has been absent from the bitcointalk community for months as well.
www.providentmetals.com has been very reliable for me and ship out in-stock inventory pretty quick. You can also reach a live human in customer service unlike most other metals dealers that take bitcoin.
www.providentmetals.com has been very reliable for me and ship out in-stock inventory pretty quick. You can also reach a live human in customer service unlike most other metals dealers that take bitcoin.