 Show Posts
|
|
Pages: « 1 2 3 4 [5]
|
Hi, I'm using bitcoind on a Linux Debian. (Compiled version) I have a lot of dust due to free bitcoin services (when I was trying to look how it work), and now, I'm facing the problem of I have a lot of dust in my wallet. (I'm used to create one BTC address by services). So basic example today : GQHNoTt9aJfQASLMrTyfdS 0.1395
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.1295
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.1195
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.1095
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.0995
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.0895
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.0795
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.07
error: {"code":-4,"message":"Transaction too large"}
bitcoin@bea:~$ ./bitcoind sendtoaddress 1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS 0.06
47510431b7edcabe3cb73e0a6e5f55d9541b76bdd65fbe0d98c9c6cd5a14e445
bitcoin@bea:~$ ./bitcoind gettransaction 47510431b7edcabe3cb73e0a6e5f55d9541b76bdd65fbe0d98c9c6cd5a14e445
{
"amount" : -0.06000000,
"fee" : -0.00840000,
"confirmations" : 0,
"txid" : "47510431b7edcabe3cb73e0a6e5f55d9541b76bdd65fbe0d98c9c6cd5a14e445",
"time" : 1382616790,
"timereceived" : 1382616790,
"details" : [
{
"account" : "",
"address" : "1LbaY34KEn6mGQHNoTt9aJfQASLMrTyfdS",
"category" : "send",
"amount" : -0.06000000,
"fee" : -0.00840000
}
]
} So the question is : How can I deduced "how size it will be". In fact I'm moving everything properly to my inputs.io account, I want to do this with the "less" transactions I can, but trying for ten minutes everytime I want to transfert is quite boring (the "error: {"code":-4,"message":"Transaction too large"}" erreur message took 30s to one minute to be applied). Is there any functions to find the "max amount with the max size" (without compiling the client again, I saw some patches to avoid this problem, but I don't like screwing the network). |
|
|
|
Can someone provide a tutorial to make it work on Linux ?
for ubuntu 12.04 I build as follows sudo apt-get update sudo apt-get install -y git-core build-essential libssl-dev libboost-all-dev libdb5.1-dev libdb5.1++-dev libgtk2.0-dev libminiupnpc-dev qt4-qmake mingw32 synaptic qt-sdk qt4-dev-tools libqt4-dev libqt4-core libqt4-gui libdb++-dev blakecoind: sudo make -f makefile.unix clean sudo make -f makefile.unix USE_UPNP=1 <snip> Doesn't work because of levelDB. /tmp/Blakecoin/src# make -f makefile.unix USE_UPNP=0
Building LevelDB ...
make[1]: Entering directory `/home/tmp/Blakecoin/src/leveldb'
make[1]: *** No rule to make target `libleveldb.a'. Stop.
make[1]: Leaving directory `/home/tmp/Blakecoin/src/leveldb'
make: *** [leveldb/libleveldb.a] Error 2 Same with upnp 0 or 1 or none. Tried this afternoon to build this with the Feathercoin leveldb directory, same trouble. Tested on Debian Wheezy, SID and Ubuntu 12.something. |
|
|
|
MFbGDVEid4AHeXMEpfqafaYWB8MSVH5swi Thanks in Advance  |
|
|
|
PeerBet : Meska Bit777 : Meska Thanks |
|
|
|
YHrX3Ch9MQxMGDW7exRkoEfhofNwbJHvxQ Thanks in advance |
|
|
|
4EdYzxwQwf3P3iDtSZRGSgYfe6CCpAm3ea Thanks in advance |
|
|
|
|
Seriously... No Linux client ?!!
Seriously... No Open Sourced ?!!
|
|
|
|
PHPkbWRVZbThgYdKZbsPTUeNpT5C3vEruD Thanks in advance |
|
|
|
YHrX3Ch9MQxMGDW7exRkoEfhofNwbJHvxQ Thanks in advance |
|
|
|
Don't know if the offer is still available : bMY1pRdTMKx7SAd2oTZrgFLVmzfjoeppEF Thanks in advance |
|
|
|
bMY1pRdTMKx7SAd2oTZrgFLVmzfjoeppEF Thanks in advance |
|
|
|
Don't know where I should post there, but just created a little monitoring tool in PHP, if you're using YaCoind on a dedicated server, it can be usefull. Just require PHP https://github.com/Meskalyn/YaCoin-php-Tools for the code. |
|
|
|
Here is the response (in French) about the hack of OVH : http://pastebin.com/c08STp9EQuick Translate (I'm French and a big customer of OVH) : Hi, to change your OVH password, you need to go to the backoffice. An email is sent to the email adresse with an unique URL. This URL is formed by 21 chars using 3 differents RAND algorythm, which every algorythim create 7 chars (7x3 = 21). After this, the client receive an email with this unique URL [snip] This is a procedure used since 7 years who didn't change. [snip] The 26th april, we (OVH) saw this problem. 2 of the 3 functions who generate the RAND number where "not really rand" (quick translate). So this "unique" URL can be bruteforced (only 1/3 of the string was RAND). This problem has been discovered the 26th of April, at 11:03:14 (Maybe French hours, GMT +1?) and has been fixed at 12:54:13. A patch have been developped to use a corrected RAND functions. Some change has been made to use 2 reals new RAND functions/algo. [snip] After, we made a big search in our database to find if other clients have been compromised, during the last 3 years. (OVH is allowed to keep 10 years of logs, according to CNIL Agreement (Wikipedia CNIL : http://en.wikipedia.org/wiki/CNIL )). Now we (OVH) are going back to 10 years to be sure... [snip] (personal note) : More about the hack & Bitcoin cumminityWe found 3 ID who has been hacked, in this 3 cases, the "bitcoin" cummunity was targeted who was using OVH services. The hacker found the exploit the 23th of April, at 22h, testing during an hour. At 23h, the exploit method was working and the first OVH ID has been hacked. The day after, 2 others Bitcoin OVH ID has been hack. We have been in contact with this clients, but the quality of the exchanges didn't help us to find the problem/security hole. One of our internal dev finally found the hole and fixed it. We certainly must find some lessons to learn in the way to speak with our customers in this kind of problems. [snip] (Line 72 on pastebin) It took a long time to communicate about this, because we seen it was a really "small" effect (not sure about my translation in this) but "only 3 clients", and we wanted to check completly if there was only 3 clients affected or more, before speaking about this issue... [snip] Since Line 86, more "commercial" speaking, I'll not translate it. Please note, I'm not working at OVH, I'm just a bitcoin user, and an OVH customer working on dedicated servers. Edit: my translation can be "really bad", I tried to do my best as quickly as I can to share the information, this email was from the OVH Mailing List called "hosting". |
|
|
|
Restriction nouvaux inscrits, il faut au moins 5 posts et 4 heures d'activité sur le forum (compteur en haut à gauche) pour pouvoir poster n'importe où
Ah merci beaucoup (Je me doutais bien, mais impossible de trouver les limites ) |
|
|
|
Tu as lui pour BIPS : https://github.com/BitcoinInternetPaymentSystem/PrestaShop que j'ai vu passé l'autre jour. Sinon, pour un autre site j'ai dû créer une adresse BTC/membre pour leur offrir la possibilité de payer par BTC, ça pèse un peu : ./bitcoind listaccounts|wc -l && du -sh .bitcoin/wallet.dat
4109
2.3M .bitcoin/wallet.dat
6053
3.1M .bitcoin/wallet.dat
8774
4.5M .bitcoin/wallet.dat
9791
4.8M .bitcoin/wallet.dat
39050
19M .bitcoin/wallet.dat
42024
20M .bitcoin/wallet.dat
49050
23M .bitcoin/wallet.dat
50011
24M .bitcoin/wallet.dat
59050
28M .bitcoin/wallet.dat |
|
|
|
Bonjour, nouvel inscrit, mais lecteur de longue date, j'ai souhaité répondre au topic de Slush : https://bitcointalk.org/index.php?topic=1976.0Mais pas de bouton reply ou autre... Une idée ? J'ai tenté une recherche, mais 360s par recherche... Ca n'aide pas trop à filtrer mes keywords... |
|
|
|
|
Bonjour.
Sera t'il possible d'être prévenu quand il sera diffusé (ou dispo en P2P, étant donné que TF1 nous bloque l'accès depuis l'étranger).
|
|
|
|
|
