Bitcoin Forum
May 12, 2024, 03:00:13 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 [30] 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 ... 95 »
581  Bitcoin / Development & Technical Discussion / Re: Ultimate blockchain compression w/ trust-free lite nodes on: May 12, 2013, 04:16:44 PM
So, I would vote for:

{Pay2Hash160, Pay2PubKey65, Pay2PubKey33} all be serialized as 21 bytes:  0x00 + Hash160.  Any Pay2PubKey variants will be bundled under that single key.
{P2SH} scripts will be serialized as 21 bytes:  0x05 + Hash160{script}. 
{EverythingElse} Will simply be the raw script. 

One problem I see with this is that it doesn't make it clean to adopt new standard scripts, without reconstructing the database in the future...

Why not hash160(txout.scriptPubKey)? I had assumed from the beginning that's what we'd be doing. "Addresses" are a UI issue - the protocol should only concern itself with scripts.

+1
this is also what I have assumed
582  Bitcoin / Development & Technical Discussion / Re: Ultimate blockchain compression w/ trust-free lite nodes on: May 11, 2013, 11:33:49 AM
I have started to experiment with this idea.
My goal is to add this hash tree to Electrum.

Each "numChildren" value (after the SumValue) can be exactly one byte, because you never have more than 256 ptrs, and each child pointer is also exactly 1 byte.  If you want to jump to a particular child, for instance, you are at node "11" and want to go the child at 3, you simply do iter->Seek("11"+"3") and it will skip "1122" and put the iterator right at "1137", which is the first database value >= "113".

Pointers can also be encoded as bits, using a fixed-size 32 bytes vector (assuming 256 pointers).
Of course variable-length storage would be more efficient, because most nodes will have sparse children, but I don't know if it is really worth the effort.
Indeed, keys will take up to 20 bytes, and node hashes will take 32 bytes anyway, so we're not adding an order of magnitude by using 32 bytes.


Quote
Furthermore, you might be able to get away without even any pointers!  You might just store the node/leaf hash and value, and know about children after the fact, simply by continuing your iteration.  You are at IterA, and IterB=IterA.Next().   You know that IterB is a child node of IterA because IterB.key().startswith(IterA.key()).   That's stupid simple.  

So, you know what level you're at simply by looking at Iter.size()
So, you know that you are a child because IterNext.key().startswith(IterPrev.key()).
If the previous check fails, you know you finished traversing that branch and you can update IterPrev.

Though, there may be something I'm missing that would still require you to store the pointers.  But it's still a lot better than storing 6-8 bytes per pointer, which was originally where I thought the bulk of the data was originally going to end up.

You can indeed do it without pointers, but iterating to find the children of a node can be very long.
And you will need to find the children of a node everytime you update its hash.


583  Bitcoin / Bitcoin Discussion / Re: List of wallets that support mBTC on: May 08, 2013, 11:24:34 AM
My knowledge is incomplete on this

that's a nice way to say it.
you could have done some basic research instead of posting a zero-knowlegde statement.
Electrum does support mBTC.
584  Bitcoin / Electrum / Re: Electrum password issue on: May 04, 2013, 09:34:50 PM
Thank you ThomasV. I used the console to do as you described and it worked out fine for me. I reset my password.

I'd like to ask. Is this not a security threat. I mean, can't anybody reset my password like this?

no, wallet was not encrypted at all. it's a bug, that will be fixed in the next release
585  Bitcoin / Development & Technical Discussion / Re: Ultimate blockchain compression w/ trust-free lite nodes on: May 03, 2013, 09:50:20 AM
subscribing
586  Bitcoin / Electrum / Re: Electrum - Bitcoin client for the common users (friendly and instant) on: May 02, 2013, 09:16:30 AM
I have a strange behaviour the first time now. I have a transaction that shows at electrum.no-ip.org, electrum.bysh.me and electrum.datemas.de as it has 0 confirmations. But when i check the same transaction id on blockchain.info it has 2 confs already.
First i thought a server isnt up to date but so many servers? The tid is:
Code:
1a112c2d29bda6a03392230d3c45717b6d8ba1307262a77d68e49c5e18fac5da

Till now electrum was always as fast as blockchain.info.

what happens if you do this in the console?

Code:
getaddresshistory("1GFEJMUeeAWcsvhnTXmGyf5NdKaqfymbou")
587  Bitcoin / Electrum / Re: [ANNOUNCE] Electrum - Lightweight Bitcoin Client on: May 02, 2013, 04:26:24 AM
as you may have noticed, in 1.7.3 imported addresses are in a separate account.
in future versions users will have the possibility to create several seed generated accounts, with change addresses.

a general principle that defines accounts is that Electrum should not mix addresses from different accounts when doing a transaction.
so when it uses account A, it will not send the change to account B.

to keep this consistent, if you use the imported addresses, the change will go to imported addresses.
588  Bitcoin / Electrum / Re: Can't set Zero transaction fees in Electrum on: May 01, 2013, 07:02:11 PM
Does it mean that transactions below the priority cannot be propagated at all or that these transactions cannot be propagated without a fee?
this question does not make sense.
there are rules in the network that determine if a tx can be propagated.
please read the documentation link I provided.

Quote
my understanding was that the user determines the fee and that it can differ from the suggested fee.
that is correct

Quote
If this truly is the case, then how does Electrum determine the appropriate fee,
the fee depends on the length.
it is the fee per kilobyte that you set in your preferences multiplied by the number of kilobytes of the transaction.

Quote
why does it not show it and why is it not just a suggestion?
what makes you think it is not the case?
589  Bitcoin / Electrum / Re: [ANNOUNCE] Electrum - Lightweight Bitcoin Client on: May 01, 2013, 04:41:43 PM
Hi folks!
(I love this client)

I have a question about the behaviour of change/prioritize addresses.
I had some bitcoins in 3 imported addresses and some in a Electron address; i wanted to use the coins in imported addresses, so I prioritize them and made the payment. There were some returned bitcoins and they were put in an imported address instead of a change address. Why? Is it because the imported address was prioritize? Is it possible avoid this?

Thanks.
Sorry my orrible English.

Previously, a user lost some coins because he expected change from an imported address to be sent back to the same imported address
(he deleted his wallet and seed, but the change was sent to an address derived from the seed)
I changed this in order to prevent that from happening again.
590  Bitcoin / Electrum / Re: Map of Electrum servers worldwide on: May 01, 2013, 01:33:05 PM
see also: http://arche.jooz.net/
591  Bitcoin / Electrum / Re: Electrum sending unconfirmed bitcoins on: May 01, 2013, 01:32:12 PM
Transaction doesn't show up on https://blockexplorer.com/ either.
I do not think that blockexplorer shows unconfirmed transactions at all.


Quote
Also transaction doesn't show up in other people bitcoin clients
which client are they using?
592  Bitcoin / Electrum / Re: Electrum can't verify a signed message on: May 01, 2013, 10:39:09 AM
this is fixed in git. please wait for the next release
593  Bitcoin / Electrum / Re: Electrum - Bitcoin client for the common users (friendly and instant) on: May 01, 2013, 10:13:04 AM
Is there a way to send multiple transactions in one transaction like its possible in original client? maybe using ; in between addresses and values? I wondered how refunds could be done with least work possible and without having to pay a fee for each transaction. For that it would be good to have such possibility. The help buttons doesnt mention such.

not for now. it's on my todolist
594  Bitcoin / Electrum / Re: Electrum - Bitcoin client for the common users (friendly and instant) on: May 01, 2013, 10:02:02 AM
Im not sure if its an error too but often when i go to receive tab all the settings are gone about how big the columns are and so on. So that i have to click everywhere to get it back. But its only sometimes, on other times it shows the settings from before. I didnt find when it happens that its set back.

yes, it's a bug.
595  Bitcoin / Electrum / Re: Electrum sending unconfirmed bitcoins on: May 01, 2013, 09:52:18 AM
Hey, I observed the exact same thing yesterday. Didn't have time to further investigate.
It eventually (as soon as the next block was resolved, I believe) went through without having to re-create the transaction.

All right, I can see the problem:
A transaction with unconfirmed inputs is not visible on blockchain.info, even though it was propagated among Electrum servers.

it seems to be a bug with blockchain.info, not with Electrum.  you are not reporting it at the right place Grin

596  Bitcoin / Electrum / Re: Random Number Seed on: May 01, 2013, 09:04:57 AM
Please read http://stackoverflow.com/questions/5480131/will-python-systemrandom-os-urandom-always-have-enough-entropy-for-good-crypto

/dev/urandom can indeed run out of entropy if it is called repeatedly.
Here we call it only once, when the wallet is generated, so this cannot happen.

The only risk i see is if your wallet is created as part of the OS install on a very simple device. Correct me if I'm wrong.


Hi Thomas, thank you for this wallet, I have really enjoyed it from an aesthetic perspective so far.

Given that a lot of people are likely to start creating wallets on a very simple device right after an OS install (debian netboot or similar), would it be wise to increase the system entropy somehow and collect randomness in a method similar to that used by GnuPG?

Thanks again for your work with the wallet!

I don't think so.
If the wallet is installed by people, then the system already has some entropy, just because of the way people interact with it.
I would be more concerned about really simple devices (such as the "trezor"), not something able to run a full debian OS, and about seeds generated during that device initialization.
I am not an expert, however; correct me if I'm wrong.
597  Bitcoin / Electrum / Re: Searching transaction history on: May 01, 2013, 08:53:49 AM
Can any one help me with any knowledge on which classes takes care of tx history. I want to create functions to seacrh through them. thank you for the help in advance.

in the console, try:
Code:
history()

or
Code:
wallet.get_tx_history()
(raw output)

598  Bitcoin / Electrum / Re: Electrum sending unconfirmed bitcoins on: May 01, 2013, 08:49:55 AM
Case for example:

1) I send some bitcoins to someone
2) Transaction shows as pending in my Electrum, and also shows up as unconfirmed on blockchain.info
3) I send some more bitcoins to someone else (before the first transaction confirms)
4) 2nd transaction shows as pending also in my Electrum

However only the 1st transaction shows up in the blockchain at blockchain.info or blockexplorer.   Until after the first transaction has been confirmed a few times then the second transaction randomly appears...

So person #2 thinks that I have not yet sent them anything, because the transaction appears only in my Electrum, but no one else on the network sees it yet.

It can be especially annoying if you need to send funds to lots of different people in quick succession.

Can anyone explain what is the deal with the missing/hiding transaction #2?


this is strange... are you sure that your observation is correct? is this reproducible?
if the second transaction showed up in your history, it means that your server has accepted it.
Servers are regular Bitcoin nodes, so they will relay your transaction to the Bitcoin network.

599  Bitcoin / Electrum / Re: Electrum - Bitcoin client for the common users (friendly and instant) on: May 01, 2013, 08:41:58 AM
Hm... i signed a message with electrum. Then i wanted to check out the message with verify. Unfortunately it always says only: "Wallet instance has no attribute 'verify_message'"
thanks for pointing that. it will be fixed soon.
600  Bitcoin / Electrum / Re: Can't set Zero transaction fees in Electrum on: May 01, 2013, 08:23:53 AM
Well it's been about two weeks or so since I've received these very special tiny coins...

Still, when I want to transfer them from Electrum, it forces me to use a transaction fee.

How old do these coins have to be before I can set a zero transaction fee ?

Thanks

D


see the technical info : https://en.bitcoin.it/wiki/Transaction_fees
if your transaction does not have a priority higher than the threshold described there, it will not be propagated by the Bitcoin network.

the Electrum client prevents you from sending a transaction that would otherwise not be propagated by the Bitcoin network.
when this protection was not there, the transaction was visible only at one server, misleading users.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 [30] 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 ... 95 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!