Bitcoin Forum
May 07, 2024, 11:35:08 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 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 81 82 83 84 85 86 87 »
1521  Bitcoin / Development & Technical Discussion / Re: WTF? bitcoin-qt Wallet Passphrase in history??? on: September 16, 2016, 02:03:27 PM
Really? That is quite strange. It works for me on multiple systems. The history is never written to the disk so it should not persist across instances of Bitcoin Core.

Not sure about being written to disk, but it definitely had to read it from the disk.
My only explanation so far would be, that some old version of bitcoin core did write this.

I have not yet restarted my server since I found out with the 0.13.0, I actually cannot claim id does write something to the disk.
But as I have restarted Bitcoin core several times on the running server  (uptime like 2 days), I can confirm that the history stored on disk - obviously, but maybe from earlier versions - 0.13.0 did read on every startup.

Let me check again:

Yup. My bitcoin-qt definitely stores history to disk, as even garbage I put in, like

walletpassphrase "shitty passphrase" timeout

appears again after I shutdown and restart my bitcoin-qt and then simply press arrow up.


of course I know what a git PR is.


Rico
1522  Bitcoin / Development & Technical Discussion / Re: WTF? bitcoin-qt Wallet Passphrase in history??? on: September 16, 2016, 01:36:13 PM
It should clear the history every time you restart Bitcoin Core. It doesn't do that when you close the debug window though.

(i found the pale blue (x))

unfortunately, v0.13.0.0-ga402396 (64-bit) doesn't clear the history at all. Not if I restart Bitcoin Core, not if restart the computer.

You're a programmer. You should submit a PR to fix this, or at the very least, open an issue and suggest it. The developers don't frequent this forum anymore.

Ok, I'll submit a press release.  Wink


Rico
1523  Bitcoin / Development & Technical Discussion / Re: Vanitygen: Vanity bitcoin address generator/miner [v0.22] on: September 16, 2016, 01:09:54 PM
I need someone who can make custom changes to vanitygen and oclvanitygen.

I would like to use them in the Collision Finders pool project instead of the address generator that is in use now (some compiled Go program).

This is still on. However, the requirement has slightly changed (and is - I believe - easier now)

Objectives:

1)

I'd need to get the output of the "gen-gocpu-xxx" executable we have now, where "gen-gocpu-linux64 X" will spill out 220 x2 hash160 values (x2, because both in uncompressed and compressed ecs form) like that:

Code:
> gen-gocpu-xxx 0

[20 bytes uncompressed for pk 1][20 bytes compressed for pk 1][20 bytes uncompressed for pk 2][20 bytes compressed for pk2]


There are no newlines etc., so you get a clean 40MiB of data blob.
Just fetch http://62.146.128.45/download/LBC-client/gen-gocpu-linux64 for comparison.
The blob of page 0 is here: http://62.146.128.45/download/LBC-client/0.btc

2)

I need to know if vanitygen is using a slower/faster SHA256 code than http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/sha-256-implementations-paper.html and in case it uses a slower one, integrate use of the intel-specific implementations.


Of course, I'm willing to pay for both objectives - 1) is prerequisite for 2) - with my precious Bitcoins. PM me, if you are capable of and interested in the job.


Rico
1524  Bitcoin / Project Development / Going no-auto on: September 16, 2016, 11:22:19 AM
Most people have used the client with the implicit/default "auto" mode for search page assignment.

I have just added this to the README FAQ which will be in the next release:
(next release will allow to run on small Amazon EC2 instances and finally, finally the Windows client is stable!)


Code:
Q: What if I want to check a specific range on directory.io?

A: Each page on directory.io lists 128 private keys and the
   corresponding uncompressed and compressed addresses. The LBC checks
   in blocks/pages of 20bit size (1048576 PKs) and is therefore like
   checking 8192 pages on directory.io
   Say you would like to use LBC to check all that is on the pages
   569716666483 to 569716830323 on directory.io, you would call
   LBC -p 69545491-69545512 -c 0
   because 69545491 = int(569716666483/8192) and
           69545512 = int(569716830323/8192) + 1
   Takes a little over 2 minutes on a modern notebook and in fact
   you have checked a bigger range 569716662272-569716834304
   (172032 pages) on directory.io

So basically, you would like to check - just for fun of course - some 100000 pages on directory.io for addresses with funds on them. You cannot do that by clicking around, unless you're a real immortalist type person. Also wget-ing doesn't even qualify as snail attempt and the LBC "auto" mode doesn't quite cut it.

Enter the above FAQ:

Because every block checked in LBC is exactly as big as 8192 pages on directory.io, all you have to do is to compute the lower and upper bound of your search interval by computing

Code:
lbc_from = int(directory.io_from/8192)
lbc_to   = int(directory.io_to/8192) + 1

and then just start LBC with

LBC -p lbc_from-lbc_to -c <num of cpus unless you're on windows in which case it's 1>

Et Voila! - you may check hundreds of thousands of pages against millions of addresses with funds on them within minutes.

A little warning:

Some people have done this already with insane numbers/ranges. This is a shortcut to the client-blacklist. Count and think before you
enter some numbers there. If you have trouble with counting and thinking, also wait for the new release, which does that for you and limits max. work to 1 day.


Rico
1525  Bitcoin / Development & Technical Discussion / Re: Running 50+ Altcoin daemons + Bitcoin? on: September 16, 2016, 10:30:58 AM
The pool bounty is 0.00666666 BTC?  Smiley

Yeah - well...  Cool

After 1AKKm1J8hZ9HjNqjknSCAfkLR4GgvCAPjq (0.00006660) and 1TinnSyfYkFG8KC3gZ72KpYxBXsxSadD8 (0.00066600) which have already been found/claimed - it's now this.

Quote
What is this project doing, by the way?

from http://lbc.cryptoguru.org:5000/about

Quote
What is LBC?

The "Large Bitcoin Collider" (LBC - a homage to LHC) is a distributed endeavour to find Bitcoin collision(s) by systematically creating addresses to known private keys and checking them against the list of known BTC addresses with funds on them. In the unlikely case of a collision, the funds on the address in question would become accessible to the collision finder.

I wanted to do something different - but please in case of interest, let's continue here: https://bitcointalk.org/index.php?topic=1573035.0
as I believe I've hijacked this thread for too long now.

So to add something to the topic here:

Running a bitcoin node, requires

  • at least 100GB hd space for the blockchain
  • at least 1.2GB RAM (*)
  • on average 30% of a Intel(R) Xeon(R) CPU E5-2630L v3 @ 1.80GHz core

Litecoin is not as stern. Don't know about other Altcoins, but I wouldn't want to run 50 full bitcoin nodes. :-P


(*) for this "bitcoin   1572 16.5 29.1 1337996 1060332 ?     SNsl Aug20 6466:29 /usr/bin/bitcoind -pid=/var/run/bitcoind/bitcoind.pid -conf=/etc/bitcoin/bitcoin.conf -datadir=/scrap/bitcoind -daemon -disablewallet -txindex=1 -maxconnections=500 -timeout=15000"


Rico
1526  Bitcoin / Development & Technical Discussion / Re: Running 50+ Altcoin daemons + Bitcoin? on: September 16, 2016, 10:10:12 AM
Actually, I have 4 physical CPUs which have 15 physical cores each. So 60 physical cores and 120 cores with hyper threading.

As I suspected.

Quote
And I have 6 of these machines here  Wink You could probably sell these machines and get a couple brand new Ferraris for it!

Holy Sh...!

I guess 12 hours of operation would shoot you straight to the top of the Top15 (http://lbc.cryptoguru.org:5000/stats) and I believe we would see the Pool bounty claimed before Midnight GMT...

A couple of Ferraris couldn't do that.

Rico
1527  Bitcoin / Development & Technical Discussion / Re: WTF? bitcoin-qt Wallet Passphrase in history??? on: September 16, 2016, 09:58:43 AM
By clicking the Clear Console button (shortcut: Control-L), which has the added benefit that your passphrase is no longer displayed right there on the screen, so why on Earth would you not clear it anyway if other people have access to your machine? Huh

There is no "Clear Console button", but Control-L works. Thanks.

I did not write other people have access to my machine, I wrote "when someone gained access". Big difference - you're welcome.

I will use Control-L from now on, but I still fail to see why this isn't default after bitcoin-qt has been closed, at least cleanse history from all critical or potentially critical information (passphrase, private keys etc.).

Quite a security risk IMHO, especially as I cannot recall to have read that big fat warning to "not forget doing Ctrl-L" after entering some sensitive information. Actually the help states Ctrl-L is for clearing the screen - not screen and history.


Rico
1528  Bitcoin / Development & Technical Discussion / Re: Converting Hash160 list to Address on: September 16, 2016, 09:09:55 AM

Simple scrypt in python


That works only with Litecoin.  Wink


Rico
1529  Bitcoin / Development & Technical Discussion / Re: Running 50+ Altcoin daemons + Bitcoin? on: September 16, 2016, 09:06:36 AM
You would need a hell of a beast.

I am running a private testnet with 350 independent instances of bitcoin.
I am on 120 Xeon E7-4880 cores with 1 TB ram ... no problems so far.


You need to go here: http://lbc.cryptoguru.org:5000/download, download the 64bit version, and run

Code:
./LBC -c 45 -t 3600

 Grin

Ok, maybe not even for an hour, but I seriously would like to see what happens. While I have some machines with 1TB RAM here, none of them has 120 cores.

I take it, your machine has 120 logical cores (that is - with hyperthreading) and therefore 60 physical cores.


Rico
1530  Bitcoin / Development & Technical Discussion / WTF? bitcoin-qt Wallet Passphrase in history??? (Bitcoin Knots) on: September 16, 2016, 08:41:36 AM
I just found out, that my wallet passphrase is kept SOMEWHERE in the history of the debug window in my bitcoin-qt client.

WTF!?

For importing private keys (or whatever other operation needs this), you have to unlock the wallet if it is protected by a passphrase.
You do this by typing

walletpassphrase "<your passphrase here>" <time>

in the CLI of the debug window to get it unlocked for a <time> limit. Now when someone gained access to the computer, and fired up the debug window, all he had to do was going up the history (arrow up) to see the passphrase in clear text.

"Ich glaube, mein Schwein pfeift" as some Germans would comment on that.

How do I get rid of this unbelievable behavior? How do I find out which "developer" is responsible for that?


Rico
1531  Bitcoin / Project Development / Re: Collision Finders Pool on: September 13, 2016, 12:30:28 PM
Attention! Windows version crashes if you try to use more than 1 CPU. And it also crashes if you want to use 1 CPU for longer periods  Roll Eyes Workaround: start in as many windows as you have/want-to-use CPUs
Code:
perl LBC -c 1 -t 1
. It's super-paranoia and super-annoying, but at the moment your best bet to participate with Windows.

I'm figuring out better ways around this situation.


Rico
1532  Local / Projektentwicklung / Re: Collision Finder Pool - German Thread on: September 13, 2016, 10:18:24 AM
Ist der auf Basis von Perl?

Perl ist sozusagen der Kleber, der die Kommunikation mit dem Server übernimmt und den/die Generatoren steuert.
Der Generator selbst ist compiliertes Go. Die ursprünglichen Sourcen sind hier: https://github.com/saracen/bitcoin-all-key-generator
Aber mittlerweile habe ich den arg getrimmt/modifiziert.

Die Windows-Version macht mich aber nicht so glücklich. Braucht elend viel (mehr) Speicher und scheint auch nicht so stabil zu sein.

edit: genau genommen stürzt sie zuverlässig ab, wenn man mehr als eine CPU auslasten will. (-c x für x > 1) Workaround: in mehreren
Fenstern einfach "perl LBC -c 1 -t 1" starten, so oft wieviele CPUs (oder Speicher) man hat/nutzen will.

Den Perl Source kann man im Editor ansehen

Code:
#!/usr/bin/env perl

use
strict;
use
warnings;

use
bignum
lib =>
'GMP';
use
utf8;

use
Config;
use
Data::Dumper;
use
Digest::MD5
qw(md5_hex);
_use_eval_cpan(
'File::Spec'
)
;
.... snipp (geht natürlich noch weiter)

Muss man zwecks besserer Lesbarkeit evtl. mit perltidy drüberhuschen.

Quote
Kann ich da den Quellcode einsehen oder ist das mit Perl2EXE in eine Exe Datei umgewandelt.
Ich lass auf meinen BTC Rechner keinen Software laufen die ich nicht kenne...

Das ist sehr vernünftig, allerdings muss die Software nicht auf einem "BTC Rechner" laufen. Da wird keine Blockchain, Wallet o.ä. benötigt.

Momentan probiere ich aus den Client auf einer kostenlosen Amazon-Instanz laufen zu lassen. Die help bekomme ich angezeigt. Aber die EC2 t2.micro kisten haben nur 1GB RAM...

Code:
[ec2-user@ip-xx-xxx-xx-xxx ~]$ sudo ./LBC -c 1 -t 60
Benchmark info not found - benchmarking... done.
Reading balances... storable found - using that (faster)... Out of memory!

Mal schauen ob mir da was einfällt...


Rico
1533  Local / Projektentwicklung / Re: Betatester für "Collision Finder Pool" gesucht on: September 13, 2016, 07:40:43 AM
Bis jetzt noch keine Adresse gefunden wo was drauf ist --> ca. 10 Mio Adressen wurden geprüft

Der Pool prüft derzeit 5 Mrd. Adressen die Stunde... mit im Schnitt 3-4 aktiven Clients.  Smiley

10mio Adressen hat mein Notebook derzeit in 25 Sekunden durch. Ich wünschte, ich würde mich besser in OpenCL oder CUDA auskennen. Die GPU im Notebook macht bei oclvanitygen 15MKeys/s - theoretisch sollte ich dadurch noch einen Speedup von ca. 30 hinbekommen.


Rico
1534  Alternate cryptocurrencies / Pools (Altcoins) / wemineltc.com #rekt? on: September 12, 2016, 02:00:31 PM
After a long (~ 2 years) time, I wanted to check my wemineltc.com account. I try to log in, and


Quote
Account Banned! See Site Staff On Issue Tracker Here: https://www.weminecryptos.com/forum/tracker/project-5-account-login-support/

Very. Well. Then. I go to the mentioned URL:


Quote
Oops! Something went wrong!

You do not have permission to view this project

Need Help?
Click here to log in
Our help documentation
Contact the community administrator

Muhaha? Of course log in doesn't work, contacting community admin yields a "failed to execute child process 'gmail' ..."

Well - at least I guess I can get rid of my credentials then. Keep up the good work guys!  Wink


Rico
1535  Bitcoin / Project Development / Re: 0.823 -> you want it on: September 10, 2016, 10:19:54 PM
Yay, downloading the new version now!

3 times faster!!! Woo!

Just curious, what did you do to get 3X the performance?

Basically I got rid of the whole base58 processing. The generator now simply creates a hash160 from uncompressed and compressed public keys.
The missing base58 munging, four SHA256 computations less per PK and the constant length of hash160 contrary to base58 (which allowed some more optimizations) summed up pretty good.

I still believe more can be done, especially with GPUs - but it's still an open quest.

Rico
1536  Bitcoin / Project Development / 0.823 -> you want it on: September 10, 2016, 11:09:45 AM
Hi all,

this is a rather large announcement and I am very excited about this. So consider all of the following text in ALL CAPS, bold, with emphasis and underlined.  Smiley

I have pushed out the new version 0.823 of the client for Linux and Windows, 64 and 32 bit. This version is a significant step towards serious collision attempts as it:

  • is about 3 times faster than the previous version!
  • however, it uses less space in memory and on disk
  • has the "persistent-found" feature as suggested by Jude Austin

The pool also offers a new bounty (1pdSSfCx4QynTwXTtVDjEEavZ4dDnYdhP) and with current search speeds it is within comfortable reach of the pool.

The pool will also have searched the equivalent of 3 billion pages on directory.io anytime soon now. Imagine clicking through that!  Cheesy

edit: As of tonight (2016-09-14 CET), the pool has searched one trillion addresses.

Rico
1537  Bitcoin / Project Development / Re: Collision Finders Pool on: September 09, 2016, 06:29:01 AM
Maybe I am being super duper optimistic but on the Statistics page of your website there should be a column for "Collisions" next to "Blocks done" for the client ID.

The clients stats will be extended (like client speed etc.), but for the "found" information there will be a separate page. LIke "What has the pool found so far, when which client had the hit, type of find (bounty/true collision) etc.

Quote
Also, could you add an option to LBC to write any collisions to a text file? This way if my computer crashes, power goes out, etc etc then I don't lose the "Collision".

Great idea. I will add that - as default behavior.

edit: although I believe some Linuxers at least solve that by doing something like ./LBC -c x -t blah | tee file.txt
but I will add it nonetheless.

Quote
I would add it but I absolutely hate Perl and refuse to even look at it, haha.

 Cheesy I have the same feelings for Python and PHP.

Seriously - if someone has ideas what to do, I will be happy to pick them up.


Rico
1538  Bitcoin / Project Development / Re: My first bitcoin startup on: September 08, 2016, 08:10:52 AM
The picture you see in my Avatar is me wearing a T-Shirt I got from https://www.shirtinator.de/
I think they have a very nice and professional process where you can design your T-shirt and get one if you wish so.

I do not see in any of the 3 ideas anything new or special. Of course, you can enter any business at any time if you think you can provide the same service/product at a better price or a better service/product at the same price as established business.

Often this means you have to work against the resources the established business has put - and continues to put - into their business. Which means you will probably not succeed if you try to perform the lone wolf stunt.

You also write you have some understanding of bitcoin and ideas. My question (as an investor to you as well as an entrepreneur to myself) would be: What skills do you have?

Rico
1539  Bitcoin / Project Development / Re: Collision Finders Pool on: September 08, 2016, 06:48:23 AM
May I ask, do you guys store private keys on a server? Because the chance of a collision is currently so miniscule, but if bitcoin picks up, someone generating and using an address in the future it's much more probable.

There is no way the server could keep up with the generated private keys. All PK generation and checking occurs on the client and after the client has checked the keys, they are discarded. All the server does is distributing chunks of work to the clients, receiving ACKs for work done and performing multi-interval arithmetic to ensure nothing is left out and nothing is done (unnecessarily) twice.

The main reason for the offline processing is speed and scalability - of course. But I also like to leave the decision what to do with a PK found in the clients hands to not get involved in case the client decides to ... hmm ... reward himself.

Right now, the pool is just getting warm. There are still few clients and - to be honest - the pool is not yet searching in the optimum keyspace (and yes: I know where that is  Cool )

As for the pk storing: I do such a thing too, see this german post: https://bitcointalk.org/index.php?topic=1587485.msg15941399
But it's only an experiment for efficient PK storage and the server I run the experiment on has to recompute the PKs again - these from the pool cannot be reused. (Well - actually I plan to have a feature in the LBC client where it will also store the generated keys on disk instead of discarding them after checking... but time oh time... So theoretically I could let run a LBC client on the PK storing machine and kill two birds with one stone.)

Rico
1540  Bitcoin / Project Development / Re: Collision Finders Pool on: September 07, 2016, 08:46:36 PM
Windows x86 clients for 64it and 32bit available

Also some client contributor stats at http://lbc.cryptoguru.org:5000/stats


Rico
Pages: « 1 ... 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 81 82 83 84 85 86 87 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!