Pages:
Author

Topic: New Pywallet 0.0.1a6 - page 5. (Read 31114 times)

legendary
Activity: 1176
Merit: 1233
May Bitcoin be touched by his Noodly Appendage
September 17, 2013, 08:29:29 AM
#6
Thanks for your interest guys.
Looks like importing features is rather easy so the next (last?) tricky task will be to implement the web server class I made.

It would be nice to see this on mac Wink
It would only require python and repairing the python bsd package (broken in osx).



A few images:

Click "..."

Select wallet.dat

Click "dump"

legendary
Activity: 1498
Merit: 1000
September 17, 2013, 04:26:00 AM
#6
It would be nice to see this on mac Wink
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
September 17, 2013, 04:23:54 AM
#5
I'm always a fan. watch-wallet and insert-random-wallet and pretending to be Satoshi were my favorite features.
full member
Activity: 220
Merit: 100
September 17, 2013, 03:24:57 AM
#4
this is fantastic.  Thank you!
hero member
Activity: 560
Merit: 517
September 16, 2013, 07:49:48 PM
#3
Very cool to Pywallet getting some much needed spring cleaning.  Besides its obvious uses, I've found it to be a useful reference for understanding how bitcoind uses BDB, quickly bringing up some ECDSA math in Python, etc.

Keep it up!
legendary
Activity: 1176
Merit: 1233
May Bitcoin be touched by his Noodly Appendage
September 14, 2013, 08:20:31 PM
#2
Progress so far



legendary
Activity: 1176
Merit: 1233
May Bitcoin be touched by his Noodly Appendage
September 14, 2013, 08:19:58 PM
#1
Pywallet is a software I forked 2 years ago. It allowed importing addresses into wallets and dumping wallets. Since then I added functionalities like deleting keys, merging wallets and building transactions, among others.
I have planned to rebuild Pywallet from scratch for a few months now.

Some reasons made this rebuilding absolutely necessary:
  • I'm far better at Python and Bitcoin
  • The amount of code I added is huge and the additions lacked logic
  • The code then became a mess and hard to maintain
  • This prevents developpers to read/check the code efficiently
  • A part of the code is from Joric and this prevents me from having a global view of the code
  • The CLI and the WUI of pywallet are totally divided, so:
    • The features that are shared by them are written twice
    • They don't even have access to the same features
  • Some dependencies are actually unnecessary
  • I'd like to have a GUI

The rebuilding has now started.
Currently the plan is:
  • Create unique feature declarations
  • Create the CLI system and make it handle the features
  • Create the GUI system and make it handle the features
  • Create the WUI system and make it handle the features
  • Easy update
  • Windows executable (only one file)
  • Make walletdump reads a passphrase
  • Implement real features*
  • Make a CSS for the WUI
  • Use Ajax in the WUI
  • Create a class instead of using global variables

The purpose of this thread is to post the progression and to read about the suggestions or comments you might have.





* Implemented features so far:
Quote
Dump your wallet
Dump your keys

Dump your transactions to a file **
Recover wallets
Import a key into your wallet
Import keys

Merge two wallets
Import a transaction into your wallet
Import a read-only address (encrypted wallets only)
Get some info about one key and sign/verify messages
Print the balance of a Bitcoin address

Delete keys from your wallet
Transaction creation
Plus those new ones:
Quote
ECDSA calculations
Dump wallets from other clients ** (Electrum, other)

** Not sure I will ever implement it



Signed files checksums (signed with 1Azzay7wH1FnDE5yZMPU57y75SuT4DbGc7):
Code:
NPW_0.0.1a.exe:
  MD5           3ebe9b641bc3511e366fa9dc868bdbef
  SHA1          bfd521ecc8364e292b1d4e7fabccfdd93c77b9c2
  SHA256        0fe5c2b8878196d1f2d3626c35b0e9f39a233e658304c9f2162aa8aad07e8a16
  SHA512        803892c90cf3b02640110d370f3fe7c1eb5fa57d943d10439e8e78b617261c38
                ea05b9ebeda20ee74c7783712837dffe314349e7d30ce16079ddf527ab19120b
NPW_0.0.1a2.exe:
  MD5           0ff99e98d5a07fddf7e7d20bce01aa63
  SHA1          01293db30497fd139e2e9415a076977ecd2b98ce
  SHA256        4da78b463b067bef501051d4f51f027c479e8706657d630273febd2576dbd288
  SHA512        5e84110cda8c51077313c00e204b52a9d2bc56053f3b618481a2fdba22f10bc5
                7d25a3aa9b1df37c29c1cdd416ff3a1804298081ad85f77827bd14ec3708e16a
NPW_0.0.1a2.py:
  MD5           464060d5ac6a702390182deb0d12ab27
  SHA1          52eb984f273975daf1173554e81c77bdcbb1add1
  SHA256        cbd79d59112d9180e2f3f2d8fb631d9a1b36dc4a0207fa3f39832325697606ed
  SHA512        a698f94fa2bb7303bc05f5f5bea5f9f43db0b3b84cb28020115ff9ef18f82e96
                c3ceabc087ce0140f8b0cdd173218c3189bf0767fbb1612a8df09e6a66a08bd6
NPW_0.0.1a3.exe:
  MD5           52e0895e4c8da43b9a78909e7772c18d
  SHA1          5bae63fe5e4827d03104b76b0b673a5900be1c1b
  SHA256        9aa688140cd6c79408d5edc59ec8f2720a063771dd77b49a59e4d0cae08ef971
  SHA512        ab1b3c72c3f66b6b4696652382fe295f423d2a714f4cccecddffa60661034610
                f3a351d8d96a2f91ed97de39e4f79e4d18e6c034b39103c06ed3616d8edf8522
NPW_0.0.1a3.py:
  MD5           8090c5fdb2800534c52ba24dec327b95
  SHA1          92592acc16752ea285617ff82818eea63ea99269
  SHA256        a7f6fe3398aec3075a228a1b9eca13246011bd4410acc9c26acac62ee7fda55e
  SHA512        599bc210abeaeee5a431bba29c018937f11e573c7d070d6e4a2574b9428a989f
                f2826c2353f931ad66bc7e7f6e9f7c93e29c11556bc3a990e3ebf9fe53e10f99
G96SnyJGBtV4tC21UvjdxznMpuMV4joDrKZNdBZa3Nd5NXL8+8gwR961xEpuSwet1umEnIVinN3zva8tygnCmHQ=

Code:
MD5:
d14d53f3231326bba42678f73e852176        NPW_0.0.1a4
Gw570HiPRLzmzbOhUhjEUy1uG1nkGj7spIuZRyP/5AhRhziKUah4NFjZj3+21YrYHcq8AQ4dGZy+xB2WVtjUPz0=



NEVER RUN A FILE I DIDN'T SIGN!
If you think one file contains a malware:
  • Tell me
  • Ask mods to remove the links pointing to it (see the message I signed below)
  • Post a link to a virustotal.com analysis



Changelog:
0.0.1a6:
- doesn't need pywallet to run
- more info about private key
- CLI if bad --ui
Pages:
Jump to: