Would anyone be interested in a LiteJack21 Blackjack service?
Sure, why not? You should be able to reuse most of the code from the other 2 sites, no? |
|
|
|
|
Kill it in 3... 2.... 1.... NOW!
|
|
|
|
|
the first "Not this again" said
|
|
|
|
|
Thanks, payment received.
|
|
|
|
I imagine if Amazon ever offers Radeon clusters, there will be a lot of interested users.
Has anyone contacted Amazon customer service to ask about this? |
|
|
|
I think I got it  Username: fun-qwert*** Balance: 409.25 Address: 1N6UQqW2ffAZeQNDVQvmWdcsDokEjRtzbC Thanks. |
|
|
|
|
Once upon a time there were two
|
|
|
|
|
Idea:
1. Include a snapshot of the blockchain in the dowload installer (updated on a regular basis)
2. Add a peer request to get the checksum of a block.
3. Have the newly installed client request checksums from peers for all blocks in the pre-loaded blockchain.
4. The checksum for each block has to be provided by at least X peers, and it has to match the checksum for the block in the pre-loaded chain.
This would simply be a way to verify with peers that the pre-loaded blockchain is valid. It would still comply with the idea of keeping things decentralized, since you wouldn't be trusting the installer, you would be trusting your peers (the same ones you would be getting the blocks from anyway).
Is there any reason why this wouldn't work?
|
|
|
|
|
One question I do have is how do imported addresses and the deterministic wallet work? You can rebuild the deterministic wallet based on the seed value, and I assume imported addresses are just held completely separate.
|
|
|
|
I will not add any support for Satoshi wallets beyond pulling keys out of them. Good decision. |
|
|
|
and then you have a deterministic wallet that is a few bytes big + hundreds of isolated keys including the backup keys. very useful.
That *is* a valid point. In many cases, it would be better to send the BTC to the Armory wallet via a transaction. Of course, the exception is vanity addresses. |
|
|
|
Put bounties for proven exploits in a test environment chainblock, under the condition of not making them public until fixed.
Agreed. And the condition is very important. |
|
|
|
 Government claims no lethal weapons, but this image surfaced underground cause police is jailing whoever contradicts them. Sticking a handgun in your waistband is incredibly dangerous and reckless, unless he has an IWB holster that I can't see. In any case, I can't believe a uniformed officer would do that. |
|
|
|
First thing I tried: import my existing wallet.dat. No go. Why ?
The one thing that a new client ought to do is allow import from
the existing established format. Either I missed how to do this
(likely), or I am flabbergasted that this one unavoidable obvious
feature was omitted. Without it ... Armory is useless.
the existing format sucks and armory has a completely different and imho way superior approach. its better to make a clean cut early than to carry on with a bad solution because of backward compatibility. its not like there a millions of people out there depending on their old addresses. Import functionality would not mean changing the Armory format. You would simply read the old wallet.dat file and then import all the private keys into the Armory wallet. |
|
|
|
Somewhere between 4 to 6 weeks?
Wrong thread?  |
|
|
|
|
Wow, that's sad. Any links to news stories about this?
|
|
|
|
Thanks for that, you cunning... oh never mind. |
|
|
|
|
I like the idea of of having 2 or 3 "pre" issues before issue #1, when it can be in B&N. That just might fly.
Issue -2 (alpha)
Issue -1 (beta)
Issue 0 (gamma/release canditate)
Issue 1 (gold release) in B&N.
|
|
|
|
|
Show Posts
