Search content
Sort by
Showing 20 of 235 results by stbgefltc
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue
Ok, then if the transaction "never made it to the blockchain":
- how can Cryptsy show it in the "Pending Deposits"?
- where are these 700 NRB? Just gone?
Is it possible that a transaction doesn't exists but the coins are gone from the wallet?
My knowledge is limited here so if you have any explanation I'm interested anyway
.
What prevents me from having the same problem again tomorrow?
Thanks again.
- how can Cryptsy show it in the "Pending Deposits"?
- where are these 700 NRB? Just gone?
Is it possible that a transaction doesn't exists but the coins are gone from the wallet?
My knowledge is limited here so if you have any explanation I'm interested anyway
.What prevents me from having the same problem again tomorrow?
Thanks again.
To put it simply :
* When you create a transaction, it is "broadcast" to the network so that everyone is aware of it (including miners)
* Miners can then decide to include your transaction in the next block or not
* If a transaction is included in a block, then "it's official".
In your case, your transaction was "seen" by Cryptsy, but never included in a block. Why that happened is probably due the stalled clients (they were rejecting new blocks past height 51172, and disconnecting clients that were not stalled as they were being considered rogue for having provided a block that was rejected). So the network got split in half, one half that kept advancing, and the other that was stalled. It seems however that miners were on the half that kept going, and they never received the transaction, so it never put in the blockchain.
There may be a way to recover your coins, but it's quite technical, I can give you a rundown if you need.
And yes, it's possible that the coins are gone while the transaction never confirms. I need to check, I think there's a way to get the unconfirmed transaction cancelled, and if there isn't, maybe I'll write up a way to do it.
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue
I tried on a second wallet, I get the same error. I will try again on two other wallets once I'm home.
But I think your transaction never made it in the blockchain. If you compare the output of both transactions, the one that I can see has a field "blockhash" saying in which block the transaction was included, while it isn't there in the output you provided for the first transaction.
But I think your transaction never made it in the blockchain. If you compare the output of both transactions, the one that I can see has a field "blockhash" saying in which block the transaction was included, while it isn't there in the output you provided for the first transaction.
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue
Hey something weird here to.
I sent some NRB to Cryptsy 7 days ago, Cryptsy is showing the incoming amount but it still has 0 confirmation.
TxID1: fca2fb5b8b8ddda3273083ff7acaed221316f4777bfa412b85ee262c7d927450
I just sent a few NRB to the same Cryptsy address and I got the 6 confirmations within a few minutes, but my first transaction is still stuck to 0 confirm.
TxID2: 955d87392bfc8a3f7b0e41310bb9a14a38afdfcc0f8ce589b37e6a419b461797
Is it a normal behavior or is the first transaction lost somewhere?
Thanks
I sent some NRB to Cryptsy 7 days ago, Cryptsy is showing the incoming amount but it still has 0 confirmation.
TxID1: fca2fb5b8b8ddda3273083ff7acaed221316f4777bfa412b85ee262c7d927450
I just sent a few NRB to the same Cryptsy address and I got the 6 confirmations within a few minutes, but my first transaction is still stuck to 0 confirm.
TxID2: 955d87392bfc8a3f7b0e41310bb9a14a38afdfcc0f8ce589b37e6a419b461797
Is it a normal behavior or is the first transaction lost somewhere?
Thanks
Hum... apparently first transaction was never seen by the network (do you see it in your wallet ? can you get info about the transaction using the console ?) :
Code:
sudo Noirbitsd getrawtransaction fca2fb5b8b8ddda3273083ff7acaed221316f4777bfa412b85ee262c7d927450 1
error: {"code":-5,"message":"No information available about transaction"}
error: {"code":-5,"message":"No information available about transaction"}
While the second one was :
Code:
sudo Noirbitsd getrawtransaction 955d87392bfc8a3f7b0e41310bb9a14a38afdfcc0f8ce589b37e6a419b461797 1
{
"hex" : "01000000010101183c6eed80aef176d80523f05f61286f016bc21373a7fcc620727cd6f17c000000004a49304602210096524d779a31654822ea803cb96a4b6a2c3dd69e068743bd98b39f1acb237d5c022100f51e8bbe613a6eead389d27b5583a6c738f79cf48dcadb5055c2db0592528a4601ffffffff0100943577000000001976a914c12309eef1a87c4d4338fee578b23aab0b70b97488ac00000000",
"txid" : "955d87392bfc8a3f7b0e41310bb9a14a38afdfcc0f8ce589b37e6a419b461797",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "7cf1d67c7220c6fca77313c26b016f28615ff02305d876f1ae80ed6e3c180101",
"vout" : 0,
"scriptSig" : {
"asm" : "304602210096524d779a31654822ea803cb96a4b6a2c3dd69e068743bd98b39f1acb237d5c022100f51e8bbe613a6eead389d27b5583a6c738f79cf48dcadb5055c2db0592528a4601",
"hex" : "49304602210096524d779a31654822ea803cb96a4b6a2c3dd69e068743bd98b39f1acb237d5c022100f51e8bbe613a6eead389d27b5583a6c738f79cf48dcadb5055c2db0592528a4601"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 20.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 c12309eef1a87c4d4338fee578b23aab0b70b974 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914c12309eef1a87c4d4338fee578b23aab0b70b97488ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"EBRWu38ZGh2N8C3mPRuXuXkQgh6MoeTVzV"
]
}
}
],
"blockhash" : "41ae18ecf1ae0d12700fdf43cc1e7a15793402c78f635b45862222e7870478cd",
"confirmations" : 34,
"time" : 1379504119
}
{
"hex" : "01000000010101183c6eed80aef176d80523f05f61286f016bc21373a7fcc620727cd6f17c000000004a49304602210096524d779a31654822ea803cb96a4b6a2c3dd69e068743bd98b39f1acb237d5c022100f51e8bbe613a6eead389d27b5583a6c738f79cf48dcadb5055c2db0592528a4601ffffffff0100943577000000001976a914c12309eef1a87c4d4338fee578b23aab0b70b97488ac00000000",
"txid" : "955d87392bfc8a3f7b0e41310bb9a14a38afdfcc0f8ce589b37e6a419b461797",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "7cf1d67c7220c6fca77313c26b016f28615ff02305d876f1ae80ed6e3c180101",
"vout" : 0,
"scriptSig" : {
"asm" : "304602210096524d779a31654822ea803cb96a4b6a2c3dd69e068743bd98b39f1acb237d5c022100f51e8bbe613a6eead389d27b5583a6c738f79cf48dcadb5055c2db0592528a4601",
"hex" : "49304602210096524d779a31654822ea803cb96a4b6a2c3dd69e068743bd98b39f1acb237d5c022100f51e8bbe613a6eead389d27b5583a6c738f79cf48dcadb5055c2db0592528a4601"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 20.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 c12309eef1a87c4d4338fee578b23aab0b70b974 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914c12309eef1a87c4d4338fee578b23aab0b70b97488ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"EBRWu38ZGh2N8C3mPRuXuXkQgh6MoeTVzV"
]
}
}
],
"blockhash" : "41ae18ecf1ae0d12700fdf43cc1e7a15793402c78f635b45862222e7870478cd",
"confirmations" : 34,
"time" : 1379504119
}
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue
really?
Status: 1377 confirmações
Date: 16-09-2013 11:28
To: Cryptsy DvUAjGjg2PcurmazxTt9HsgnhJjZVFmsZP
Debit: -20.00 Noir
Net amount: -20.00 Noir
Transaction ID: e55b9fae4d459ae2934bd12a4e0f1831114033e07cef724b9980abf648830b28
The above transaction is still not listed in cryptsy balance!
I also have a -120NRB in balance (yes...minus..how is that possible) and 280NRB without confirmations!
My friend did not receive the coins i sent, and he cant send coins to cryptsy also..so the issue is still here for at least 2 persons!
Please look at this.
P.S. - by the way...SBC (Stablecoin) as the same issue! it never arrives to Cryptsy balance!
I have sent another 1NRB and finally it got to balance! Unfortunatly, since i have minus balance i end up with -119 instead of +1 balance!
Regards
G
Status: 1377 confirmações
Date: 16-09-2013 11:28
To: Cryptsy DvUAjGjg2PcurmazxTt9HsgnhJjZVFmsZP
Debit: -20.00 Noir
Net amount: -20.00 Noir
Transaction ID: e55b9fae4d459ae2934bd12a4e0f1831114033e07cef724b9980abf648830b28
The above transaction is still not listed in cryptsy balance!
I also have a -120NRB in balance (yes...minus..how is that possible) and 280NRB without confirmations!
My friend did not receive the coins i sent, and he cant send coins to cryptsy also..so the issue is still here for at least 2 persons!
Please look at this.
P.S. - by the way...SBC (Stablecoin) as the same issue! it never arrives to Cryptsy balance!
I have sent another 1NRB and finally it got to balance! Unfortunatly, since i have minus balance i end up with -119 instead of +1 balance!
Regards
G
You should probably contact Cryptsy's support for the missing transactions, there's not much we can do from here...
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Yes, I tested too, Cryptsy sees the pending deposit, but it never confirms, which leads me to believe their blockchain is stalled too.
I will update the OP with new version announcement once the Windows client is updated too.
I will update the OP with new version announcement once the Windows client is updated too.
Dont see mine as pending, you know if http://nrb.miners-united.com/ on the right blockchain?
From what I've gathered there is only one blockchain (a bit above 55K blocks as of now), but some clients are choking on it, and they stop syncing at height 51712. So there is no real fork going on.
Send me via PM your user name (and transaction ID if you have it), I will investigate on that.
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Yes, I tested too, Cryptsy sees the pending deposit, but it never confirms, which leads me to believe their blockchain is stalled too.
I will update the OP with new version announcement once the Windows client is updated too.
I will update the OP with new version announcement once the Windows client is updated too.
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Sorry, spent the last couple days investigating the issue, so I haven't been very present...
There was an old bug laying around which has been causing some blocks to be rejected when they shouldn't have. From the looks of it, there is no fork though, which is fortunate. Most clients just stopped syncing past height 51712.
I have pushed an update on Git for those running *nix, you can go ahead and recompile the new client. As soon as I get home, I will publish an updated Windows client, unless some good soul wants to take care of it before I get a chance.
For those transferring coins to Cryptsy, they are not arriving most likely (this is pure speculation, I cannot state this as a fact) because Cryptsy's client is stalled too. Once they update, you should receive your coins.
There was an old bug laying around which has been causing some blocks to be rejected when they shouldn't have. From the looks of it, there is no fork though, which is fortunate. Most clients just stopped syncing past height 51712.
I have pushed an update on Git for those running *nix, you can go ahead and recompile the new client. As soon as I get home, I will publish an updated Windows client, unless some good soul wants to take care of it before I get a chance.
For those transferring coins to Cryptsy, they are not arriving most likely (this is pure speculation, I cannot state this as a fact) because Cryptsy's client is stalled too. Once they update, you should receive your coins.
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Sorry guys, I was gone on vacation for a week...
@John122 : Yes, Noirdice is undergoing redesign, and adding in provably fair betting too...
@TheRickTM : Yes, I have done some work on merged as that was the original goal for Noirbits. Got a bit caught up with time though, but that's the next upcoming feature.
@John122 : Yes, Noirdice is undergoing redesign, and adding in provably fair betting too...
@TheRickTM : Yes, I have done some work on merged as that was the original goal for Noirbits. Got a bit caught up with time though, but that's the next upcoming feature.
So whats the deal with Cryptsy? I see Noirbits is back on there but the latest update on nrb.miners-united.com says that the NRB mined there cannot be sold/traded on Cryptsy. But then it links to this discussion and the title says that it is "back on cryptsy".
So whats the deal? Can I send the NRB from my nrb.miners-united.com account to Cryptsy or is it just going to get stuck? I dont know what is more accurate...this thread or the last update on miners-united.
Yes, I confirm Noirbits from the pool do get in on Cryptsy. I posted an updated statement there to lift the confusion...
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Sorry guys, I was gone on vacation for a week...
@John122 : Yes, Noirdice is undergoing redesign, and adding in provably fair betting too...
@TheRickTM : Yes, I have done some work on merged as that was the original goal for Noirbits. Got a bit caught up with time though, but that's the next upcoming feature.
@John122 : Yes, Noirdice is undergoing redesign, and adding in provably fair betting too...
@TheRickTM : Yes, I have done some work on merged as that was the original goal for Noirbits. Got a bit caught up with time though, but that's the next upcoming feature.
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Just wanted to thank our Noirbits traders and miners with their own Cryptsy.com avatar. We will be giving coins away and merchandise randomly to folks who sport a cryptsy avatar on any coin forum that we spot.
Good news
Thanks for supporting us too !Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Sorry - just saw this. I am replacing the block explorers with local daemons so I can get hashing speed. Just fixed Noirbits.
Thanks a lot! Seems that also fixed CoinChoose.
That's what I meant - fixed the Noirbit numbers on CoinChoose (and a few others).
Thanks for your work !
Re: [ANN] Noirbits TAKEOVER ! Update v2.2.4.0 with new RPC calls - Back on Cryptsy !
Well I did contact Diatonic about this last week, he said he was overrun but would try to manage it at some point. He did update, but his blockchain is still wrong...
If there are any volunteers for setting up an alternative block explorer, it'd be great.
Considering CoinChoose and most coin choosers, they actually base their data off the block explorer, explaining why they are not in sync with us. But as you said, it might be better that way until the coin gains more hash power.
If there are any volunteers for setting up an alternative block explorer, it'd be great.
Considering CoinChoose and most coin choosers, they actually base their data off the block explorer, explaining why they are not in sync with us. But as you said, it might be better that way until the coin gains more hash power.
Re: [ANN] [UBERCOIN] Working on a new coin. Will update this thread when completed.
I like it. I figure that the QT client must have something similar in it, as it is able to present a confirmation dialog to the user before sending that shows the fee, and the send can be cancelled at that point. So it would seem that the code exists, and just needs to be exposed in the RPC api. Your proposal seems good to me.
Yeah, the QT part tries to send the tx, but the wallet raises an error when fee is not high enough. So the UI then asks the user to accept min. fee, which is calculated by the wallet, at which point it retries to send the transaction with proper fees when the user accepts. Porting that flow to RPC is no biggie, but the logic is a bit different.
You have to keep in mind that the transaction, in the UI, will go through if no fee is required. Here, we do not want the transaction to go through. I don't remember the exact code, there might be some refactoring in order to separate actual sending from fee calc, but it's still no biggie
Re: [ANN] [UBERCOIN] Working on a new coin. Will update this thread when completed.
The characters here are almost as entertaining as Monty Python's Flying Circus.
Inspiring to see a group taking form (out of the conscious flog) with great unconscious comedic talent.
Noting a particularly apt likeness to the Meaning of Life or Life of Brian.
Inspiring to see a group taking form (out of the conscious flog) with great unconscious comedic talent.
Noting a particularly apt likeness to the Meaning of Life or Life of Brian.
And you have no idea how much fun I had with you. You're great, man, just great ! A little poke, and you're here, back on the tracks, defending your higher order intelligence.
Speaking of unconscious talent, you're a rock star in that area
Re: [ANN] [UBERCOIN] Working on a new coin. Will update this thread when completed.
Yeah, their unpredictable nature is what's causing problems. They increase as the number of transactions to be included in the next block increases. We could revise the system, but don't forget that it's a valuable anti-DDoS tool : the rising cost prevents from pushing spam transactions on a block, as it makes the attack expensive.
Re: [ANN] [UBERCOIN] Working on a new coin. Will update this thread when completed.
Simple fact is, arguing about something never got anything done.
It amuses me that these in the "know" never actually have anything substantial to show....too much time spent procrastinating about what they can do, instead of backing it up IMO.
Basically everyone can say they have the biggest cock, but all bets are off until the cocks are on the table.
It amuses me that these in the "know" never actually have anything substantial to show....too much time spent procrastinating about what they can do, instead of backing it up IMO.
Basically everyone can say they have the biggest cock, but all bets are off until the cocks are on the table.
Well, he does have CoolPages. But I'm gonna stop there, I said I was out of this argument :p
UPDATE : Regarding the fee calculation, the following RPC calls would be nice to have :
preparetransaction(sendAddress, amount, maxFee, lockInputs)
Prepares a transaction by using the following parameters :
sendAddress : b58 encoded destination address
amount : amount of coins to send.
maxFee : maximum fees the sender is willing to pay, or -1 to specify no limit.
lockInputs : whether the inputs used to prepare the transaction should be locked. This feature is mostly for wallets with high volumes of outgoing transactions, to ensure coins stay available until the
Return value : a JSON object { hex: "signed tx raw data", fee: "0.1" }, where hex contains the signed raw data for the transaction , ready to be passed to sendrawtransaction. fee contains the fee amount that has been included in the transaction when this fee does not exceed the user specified limit. If the required fee exceeds the user specified limit when he passed a positive value to maxFee, an error object is returned with a message stating the required transaction fees exceed the user's limit.
canceltransaction(hex)
Cancels a prepared transaction by using the following parameters :
hex : raw data of a previously prepared transaction.
Return value : boolean indicating success or not.
This call would be required in case preparetransaction was called with lockInputs = true.
If the user is satisfied with the prepared transaction and the applied fees, he can then submit the hex data to sendrawtransaction to broadcast his transaction on the network and get the transaction's ID.