Bitcoin Forum
October 07, 2022, 01:45:17 AM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 »
1  Bitcoin / Development & Technical Discussion / Re: A Protocol Question from Stack Exchange on: May 28, 2013, 02:40:50 PM
https://en.bitcoin.it/wiki/Satoshi_Client_Block_Exchange
2  Bitcoin / Development & Technical Discussion / Re: Bitcoind transaction notification on: May 28, 2013, 02:16:52 PM
Actually, there are two command line switches -blocknotify and -walletnotify which will call a command when a block is found and when transactions arrive.

Honestly, I would avoid using listsinceblock, it doesn't behave as you'd expect and it'll come back to bite you.
3  Bitcoin / Bitcoin Technical Support / Re: how to check an txid input coin has been spend or not ? on: May 23, 2013, 01:16:18 PM
Where is that pool? Disk? Not RAM I suppose...

LevelDB (it's what the chainstate directory is for). It's partially cached in RAM though.
4  Bitcoin / Bitcoin Technical Support / Re: how to check an txid input coin has been spend or not ? on: May 23, 2013, 12:29:58 PM
There is a pool of unspent outputs.
a pool of ALL unspent outputs ?

Yes, you can see its size with the command 'gettxoutsetinfo'.

Yeah. ALL unspent outputs. I'm not sure how to query it.

You don't, at least not without modifying the client to add a new RPC command.
5  Bitcoin / Development & Technical Discussion / Re: Bounty: A zero-confirm modified bitcoind on: May 21, 2013, 02:35:32 PM
Satoshi-dice is based on BitcoinJ. One of the example projects is called PingService which listens for incoming transactions and then sends them back where they came which is pretty much the entire functionality of Satoshi-dice.
6  Bitcoin / Bitcoin Technical Support / Re: Dat Transaction Confirmation Time... on: May 21, 2013, 06:55:14 AM
There was no fee, so you're only chance is to get in by priority. You tried to spend an output which was only 2 days old and only 1BTC. Priority is calculated as age*amount, so there's going to be lots more transactions with higher priority which come before yours. So your only chance is to get lucky where a couple of quick blocks in a row flush out all the waiting transactions, or you have to wait for your inputs to get older so your priority increases sufficiently.
7  Bitcoin / Development & Technical Discussion / Re: Plot "block size = f(block height)" on: May 20, 2013, 05:20:03 PM
You could view source and copy the javascript data.

Code:
series: [{                   
  name: 'MB',
  data: [[1231006505000, 2.71E-4],[1231092905000, 0.0],[1231179305000, 0.0], ... ],
  showInLegend: false               
}]

The data is averaged over the day though, so maybe you need more detail.
8  Bitcoin / Development & Technical Discussion / Re: Plot "block size = f(block height)" on: May 20, 2013, 04:58:22 PM
Like this?
9  Bitcoin / Bitcoin Discussion / Re: Say Bob sends Alice on: May 20, 2013, 04:28:39 PM
about 200 transactions, each transaction has no tx and is signed by the last transaction, will Alice have to wait for a long period to receive the funds? Can Alice speed it up?
Huh
I believe he meant "no transfer fee".

Ahh - not sure why I couldn't work that out myself!

Anyway, the answers are that it will indeed take a long time to receive the funds (you're extremely unlikely to get more than one transaction into each block at a time), and currently the way the transactions are selected into a block in the reference client means there is no way to speed it up if miners are running unmodified clients.

This thread is relevant. Someone is doing the exact thing you describe.
10  Bitcoin / Bitcoin Discussion / Re: Say Bob sends Alice on: May 20, 2013, 02:38:52 PM
about 200 transactions, each transaction has no tx and is signed by the last transaction, will Alice have to wait for a long period to receive the funds? Can Alice speed it up?
Huh
11  Bitcoin / Development & Technical Discussion / Re: Blockchain parsing on: May 19, 2013, 11:08:56 PM
Anyone know the solution to this problem?

https://en.bitcoin.it/wiki/Protocol_specification#Variable_length_integer

Read the first byte as uint8 and check its value, you have 4 choices,

<0xFD:          use the value as it is
  0xFD:           read 2 more bytes as uint16
  0xFE:           read 4 more bytes as uint32
  0xFF:           read 8 more bytes as uint64
12  Bitcoin / Development & Technical Discussion / Re: Why isnt this confirming? Over 0.01 under 10k size, even includes a fee... on: May 18, 2013, 05:21:31 AM
Your transaction is large and your inputs are young and small, so the transaction has very low priority, so it's unlikely to get selected for the free part of the block. And your fee/kB is also tiny, so it won't get selected based on that either.
13  Bitcoin / Development & Technical Discussion / Re: Why isnt this confirming? Over 0.01 under 10k size, even includes a fee... on: May 18, 2013, 01:08:16 AM
Well thats a HUGE issue, if the change generated by your tx is going to get flagged as dust and thus your tx will never confirm.

How could no one have thought of or picked up on that!?

This will only be a problem if the mining pools all switch to 0.8.2 and you use a client version (< 0.8.2) which generates dust change outputs.
14  Bitcoin / Development & Technical Discussion / Re: Why isnt this confirming? Over 0.01 under 10k size, even includes a fee... on: May 18, 2013, 12:52:49 AM
Sorry, talking crap - had it in my head that the new dust checks were already included in 0.8.1, so most nodes would reject the tx.
15  Bitcoin / Development & Technical Discussion / Re: Why isnt this confirming? Over 0.01 under 10k size, even includes a fee... on: May 18, 2013, 12:44:48 AM
Your second output is considered 'dust', so your transaction won't get relayed.
16  Bitcoin / Development & Technical Discussion / Re: Is there any way to differentiate between BTC vs LTC vs altcoinX addresses? on: May 17, 2013, 02:42:45 AM
https://en.bitcoin.it/wiki/List_of_address_prefixes
17  Bitcoin / Development & Technical Discussion / Re: Automatic personalized wallet generation - any limits? on: May 17, 2013, 01:58:43 AM
Looking at multiple sites that exchange Bitcoin, I noticed that a number of them offer a way to deposit Bitcoin in your account by sending it to some personalized Bitcoin address.

The method in which these are generated makes me think that there must be one or more such addresses for each account.

Are there any estimates as to how many accounts on these sites need to be created to consume any appreciable portion of the total number of addresses available?

2160 possible address hashes, 232 people on the planet. So each person could have 2128 addresses each. That's
100,000,000,000,000,000,000,000,000,000,000,000,000 addresses each. So even if you sign up to 1000's of these sites, you'll never make a dent.
18  Bitcoin / Development & Technical Discussion / Re: A bit of criticism on how the bitcoin client does it on: May 16, 2013, 04:57:36 PM
Again: this wastes a hell lot of bandwidth, generating lots of traffic in the network each time a new block is mined.
No. That's not how it works.

I believe that I understand the purpose of the locators very well - and that is why my implementation always sends only one locator
If you do this after the last checkpoint, you're in for a surprise. Good luck.
19  Bitcoin / Development & Technical Discussion / Re: A bit of criticism on how the bitcoin client does it on: May 16, 2013, 04:01:33 PM
Actually, if you look at this article it even clearly advises:
Quote
To create the block locator hashes, keep pushing hashes until you go back to the genesis block. After pushing 10 hashes back, the step backwards doubles every loop
Yeah, you are only at block 236k+, so just keep pushing all the hashes, starting from the top, until you reach the genesis block - a brilliant idea Wink

What's wrong with this? It sounds to me like you don't understand the purpose of the locators.
20  Bitcoin / Development & Technical Discussion / Re: btcd: a bitcoind alternative written in Go on: May 16, 2013, 01:51:26 AM
Hang on - why are you trying to put the blockchain in a leveldb database?
Pages: [1] 2 3 4 5 6 7 8 9 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!