Bitcoin Forum
May 12, 2024, 10:51:36 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: BTC-E Nonce Generation  (Read 6963 times)
CoinFarmer
Member
**
Offline Offline

Activity: 205
Merit: 10


Upfiring Team Member


View Profile WWW
January 29, 2014, 11:08:08 PM
Last edit: September 04, 2017, 07:40:29 PM by CoinFarmer
 #21

I fixed nonce issue - it was format issue, but the Sign Key issue exists.
1715511096
Hero Member
*
Offline Offline

Posts: 1715511096

View Profile Personal Message (Offline)

Ignore
1715511096
Reply with quote  #2

1715511096
Report to moderator
1715511096
Hero Member
*
Offline Offline

Posts: 1715511096

View Profile Personal Message (Offline)

Ignore
1715511096
Reply with quote  #2

1715511096
Report to moderator
1715511096
Hero Member
*
Offline Offline

Posts: 1715511096

View Profile Personal Message (Offline)

Ignore
1715511096
Reply with quote  #2

1715511096
Report to moderator
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715511096
Hero Member
*
Offline Offline

Posts: 1715511096

View Profile Personal Message (Offline)

Ignore
1715511096
Reply with quote  #2

1715511096
Report to moderator
1715511096
Hero Member
*
Offline Offline

Posts: 1715511096

View Profile Personal Message (Offline)

Ignore
1715511096
Reply with quote  #2

1715511096
Report to moderator
JackH
Sr. Member
****
Offline Offline

Activity: 381
Merit: 255


View Profile
November 10, 2014, 04:45:36 PM
 #22

We are having problem with this exact issue. Does anyone have a more comprehensive tutorial on how to communicate with the BTC-E API without getting the following response every time:

{success=0, error=invalid nonce parameter; on key:0, you sent:'', you should send:1}

<helo> funny that this proposal grows the maximum block size to 8GB, and is seen as a compromise
<helo> oh, you don't like a 20x increase? well how about 8192x increase?
<JackH> lmao
ElectricMucus
Legendary
*
Offline Offline

Activity: 1666
Merit: 1057


Marketing manager - GO MP


View Profile WWW
November 11, 2014, 06:24:01 PM
 #23

We are having problem with this exact issue. Does anyone have a more comprehensive tutorial on how to communicate with the BTC-E API without getting the following response every time:

{success=0, error=invalid nonce parameter; on key:0, you sent:'', you should send:1}

You've seen that?
https://bitcointalk.org/index.php?topic=122006
JackH
Sr. Member
****
Offline Offline

Activity: 381
Merit: 255


View Profile
November 12, 2014, 11:56:44 AM
 #24

Yes I did, but we solved it. The problem was: The libraries was not sending the data in binary format, but in a text format. Our dev redid everything manually without using the library and send it as binary. That worked.

<helo> funny that this proposal grows the maximum block size to 8GB, and is seen as a compromise
<helo> oh, you don't like a 20x increase? well how about 8192x increase?
<JackH> lmao
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!