Bitcoin Forum
June 16, 2024, 05:25:08 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 [224] 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 ... 291 »
4461  Bitcoin / Development & Technical Discussion / Re: Getting block headers on: April 20, 2013, 11:34:53 AM
Thanks!


I didn't see your edit
There is a new field in the version message you send which tells the other peer not to send you inv's like this.
Thanks a lot, that'll clean my display

To receive block headers, you need to ask with a 'getheaders' message, it doesn't follow the 'getblocks' -> receive 'inv' -> 'getdata' -> receive block  message sequence.
Yeah, I was mixing getheaders and getblocks
4462  Other / Off-topic / Re: Satoshi Nakamoto - 1,5 million Bitcoins - We need answers on: April 20, 2013, 10:58:07 AM

+1, brother
4463  Bitcoin / Development & Technical Discussion / Re: Getting block headers on: April 20, 2013, 10:57:24 AM
Absolutely
Does this change anything? I didn't saw anything about it
I didn't finish reading https://en.bitcoin.it/wiki/Satoshi_Client_Block_Exchange though


Edit:
I just checked what the two responding nodes (localhost and 98.26...) and it looks like they are sending me their last blocks
localhost is sending me hashes of blocks number ~134k
4464  Bitcoin / Development & Technical Discussion / Getting block headers on: April 20, 2013, 09:55:35 AM
Hi
I ran into something strange when I'm downloading block hashes from bitcoin nodes (let's call my script 'BD')
When I'm connecting to 63.247.147.163 (all fallback nodes on the wiki* behave the same way), the following happens:
  • BD sends version
  • BD receives version and verack
  • BD sends verack
  • BD regularly receives tx inv's (about 1 per second)
Moreover, sending getblocks doesn't change anything and I still receive only tx inv's

On the other hand, when I connect to my local bitcoin node (127.0.0.1 ofc), that becomes:
  • BD sends version
  • BD receives version and verack
  • BD sends verack
  • BD receives tons of block hash inv's (yeah, TONS OF THEM)
I didn't even try to send a getblocks...


So, why does my local node behaves differently than the other ones?



(*) all the nodes I tested on http://blockchain.info/connected-nodes too



Edit: 98.26.149.98:8333 sends me some block headers after a getblocks
4465  Alternate cryptocurrencies / Altcoin Discussion / Re: Beware of compatible addresses on: April 19, 2013, 05:15:13 PM
Anyone having the private key can use ALL the corresponding addresses, whatever the *coin
Resolving this issue just requires either honesty from the receiver or a brain in the sender's head (come on, always double check ffs)
4466  Bitcoin / Development & Technical Discussion / Re: Pywallet: manage your wallets/addresses/keys/tx's on: April 19, 2013, 05:06:32 PM
1. Your wallet isn't corrupted.
2. Did you try deleting all the tx's?
3. Did you check on blockchain.info if your tx is shown?
4. Can you post the recipient address?
4467  Alternate cryptocurrencies / Altcoin Discussion / Re: How do you create an altcoin? on: April 19, 2013, 07:03:32 AM
It would require changing 1 line of code
4468  Bitcoin / Development & Technical Discussion / Re: Pywallet: manage your wallets/addresses/keys/tx's on: April 19, 2013, 07:00:06 AM
Hi! I've tried to use pywallet (current jackjack-jj master) to delete some long unconfirmed transactions from my 0.8.1 wallet.dat, per the instructions at...

https://bitcointalk.org/index.php?topic=85689.msg944529#msg944529

After the deletions, the client no longer reports the transactions in 'listtransactions' or 'gettransaction'... so far so good. But, it doesn't seem to have rediscovered the still-unspent old outputs. A launch with '-rescan' didn't help.

Did I miss a step? Does something else about the 0.8.1 indexing need to be reset/rebuilt?

 
So you deleted the tx, you made the rescan, and after that the client still doesn't show the deleted unconfirmed transaction?
If so, the client should definitely count your unspent coins in your balance
Did you check on blockchain.info if the transaction really never broadcasted?
4469  Bitcoin / Development & Technical Discussion / Re: Pywallet: manage your wallets/addresses/keys/tx's on: April 19, 2013, 06:53:24 AM
People are boring... maybe if I uploaded the wallet.dat file to some public space ... gotta make it look a little interesting. Perhaps the DDoS attacks will stop as "they" will attempt cracking this.
Sadistic but funny!
4470  Bitcoin / Bitcoin Technical Support / Re: can't use my wallet? error -30974 on: April 18, 2013, 08:39:18 PM
I don't know if I am doing something wrong, but when I go to import.

I got a lot of errors like this when I tried to import:
2013-04-18 11:22:19-0500 [HTTPChannel,1,127.0.0.1] Hexadecimal private keys must be 64 or 66 characters long (specified one is 34 characters long)

I think you're trying to import a private key in WIF format: so you must uncheck the 'hexadecimal' check box
4471  Alternate cryptocurrencies / Announcements (Altcoins) / Re: BBQCoin, the coin you want to eat. on: April 18, 2013, 04:05:39 PM
Can someone post the IP:port of a permanent BQC node?
4472  Local / Discussions générales et utilisation du Bitcoin / Re: grondilu n'est plus modérateur ? on: April 18, 2013, 03:01:22 PM
Ok, je plussoie FTWbitcoinFTW, merci pour ton boulot!
Tu restes quand même sur le forum?
4473  Bitcoin / Development & Technical Discussion / Re: Pywallet: manage your wallets/addresses/keys/tx's on: April 18, 2013, 12:19:55 PM
Not bad
Not many people seem to be interested though
4474  Local / Discussions générales et utilisation du Bitcoin / Re: Suspension du service Instawallet: processus de remboursement on: April 18, 2013, 08:20:47 AM
Tu as un numéro de rapport de police/BEFTI?
4475  Local / Discussions générales et utilisation du Bitcoin / grondilu n'est plus modérateur ? on: April 18, 2013, 08:06:24 AM
Tout est dans le titre
4476  Bitcoin / Development & Technical Discussion / Re: Entropy during private key generation on: April 18, 2013, 07:28:12 AM
I believe the client uses openssl to generate random bytes
4477  Bitcoin / Bitcoin Technical Support / Re: can't use my wallet? error -30974 on: April 18, 2013, 07:25:12 AM
If you're going to import the 100+ keys from your wallet you should use pywallet's ability to import a file full of private keys
4478  Bitcoin / Bitcoin Technical Support / Re: Listening behind a router on: April 18, 2013, 07:22:30 AM
Thanks guys
Do we know the ratio outgoing-only/upnp enabled clients?
4479  Alternate cryptocurrencies / Altcoin Discussion / Re: Stop cloning scamcoins! on: April 17, 2013, 10:38:01 PM
Please, stop making useless clones of bitcoin and litecoin without any clear-cut idea.
Lol
4480  Bitcoin / Bitcoin Technical Support / Listening behind a router on: April 17, 2013, 08:38:50 PM
I'm not really into networking and I'm wondering how satoshi client can listen to ports behind a router
I know that upnp does that, but even when I compiled (I may be wrong, it's years ago) without upnp, it's still able to connect to the network (that famous 8-limit)

So:
  • Is it possible to listen behind a router without upnp? If so, how?
  • Or is it connecting to 8 nodes (that have open ports) instead of listening?
Pages: « 1 ... 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 [224] 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 ... 291 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!