Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add namecoin qt #30

Closed
wants to merge 104 commits into from
Closed

Add namecoin qt #30

wants to merge 104 commits into from

Conversation

doublec
Copy link
Contributor

@doublec doublec commented Oct 1, 2013

This merges namecoin-qt into master. It merges in the master branch from namecoin-qt/namecoin-qt and the namecoin-qt branch from namecoin/namecoin.

To build namecoind:

$ cd src
$ make USE_UPNP= namecoind

To build namecoin-qt

$ qmake "USE_UPNP=-"
$ make

namecoin-qt and others added 30 commits May 25, 2013 11:07
src/qt will be moved to namecoin, the rest will be deleted
Seems that the original history for these files (from bitcoin repo) will
be lost.
I compiled it in MinGW, Linux may require minor changes in qmake
project.
Note: wallet encryption will make the wallet inaccessible for the
daemon. Soon I'll update the daemon with 'walletpassphrase' etc.
walletpassphrase and related commands, privkey dump/import, GUI
improvements: ran Qt lupdate on translation files to fix line numbers,
progress bar (simple - based on block count, not tx count), tray icon
remaining after exit. Set version to 3.55.
qt: register metatype for bool*

This allows the bool* type to be passed between threads.  Should solve issue #2402.
This reverts commit 95ca4f8.

We now use the same privkey format as Bitcoin.
Keys are usually 279 bytes long, but I got one of size 278 in my wallet. Eventually we should move towards Bitcoin approach of storing 32-byte secret only (and derive priv/pub key from it).
Small refactoring - moved a function from keystore.h to .cpp.
Speed up block downloading
Transaction tab now shows names too (except unused name_new
transactions, for which only hash can be shown). For names created from
GUI, a pending name_firstupdate is created and stored in the wallet.dat
as a special entry (not as transaction). It is auto-broadcasted after 12
blocks. During that period it can be edited (but cannot be cancelled -
name_new from GUI tab always performs corresponding name_firstupdate).
After that, each edit will send name_update with fee.

If automatic firstupdate fails, it writes hex to debug.log (search for
"Automatic name_firstupdate"). In this case you can only retry manually.

namecoind and RPC console in the GUI work as usual, they won't do auto
name_firstupdate.
phelixnmc and others added 29 commits August 26, 2013 11:46
I don't like it either but we should go along for now...
I don't like it either but we should go along for now...

The D:\ in run_qmake.bat is still pretty ugly IMHO.
Structured pull request for my changes.
Porting some fixes from Bitcoin, EasyWinBuilder v0.3
- Renamed rpc.* to bitcoin.* (for some reason it did not rename when merging the previous pull request)
- Added whitespace to comments of the form /*=0*/ , otherwise Qt shows warnings (it detects such comments as some meta-information)
- Removed outdated stuff from contrib directory
We use Bitcoin privkey address (version byte = 128), while vanitygen uses version byte = 180.
Version 0.3.70.
Removed excessive messages in debug.log
Fixed displaying of transferred names and corresponding transactions.
EasyWinBuilder: Fix disassembly hash differences due to system language/locale.
"map":{"*":{"ip":"1.2.3.4"} instead of "map":{"*":"1.2.3.4"}
Conflicts:
	src/allocators.h
	src/bitcoinrpc.cpp
	src/key.cpp
	src/key.h
	src/makefile.linux-mingw
	src/makefile.osx
	src/makefile.unix
	src/rpc.h
The 'cryptopp' library can't build with clang, the default compiler
on Mac OS X 10.8. To work around this I use the gcc compiler for the
'cryptopp' files and clang for the rest.

To install standard 'gcc' on Mac OS X using homebrew:

  $ brew tap homebrew/dupes
  $ brew install apple-gcc42
@doublec doublec closed this Nov 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants