Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - domob

Pages: [1] 2 3 ... 18
1
General Discussion / Re: Huntercoin 1.3.01 >> Download and info
« on: July 09, 2016, 02:01:37 PM »
And another time:  I've just updated the chain download, now it is up-to-date until block 1,295k.

2
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: May 28, 2016, 09:03:43 AM »
No, it does not use IRC.  So yes, since we have no DNS seeds and no hardcoded nodes (both can be fixed easily in the future), you need to -connect or -addnode to get some initial connections.  (But once you are up to speed, it should remember the list of nodes and then connect without issues to them; at least that's how it goes for me).

3
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 25, 2016, 08:38:47 PM »
I've now also hacked together "game_waitforchange" for the new client - I still believe that the technically better solution for the future is using ZeroMQ, but that should allow existing clients to better work with the new daemon.  Together with some work I did over the weekend, I have now everything implemented that was on my todo list for using the client as gaming daemon and wallet.  Finishing the last remaining pieces for it to be used as miner is next.

4
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 24, 2016, 09:48:00 AM »
Regtest mode is not supposed to be used for that many blocks (from upstream Bitcoin), I guess that's what causes the issues.  But I can look into that, although I think it is not top priority right now.

I agree that we need a way to test the forks.  For now I did not yet work on that, as I mainly use regtest mode for testing basic game transaction integration; the game logic itself is mainly copied and tested by syncing the chain anyway.  But at least when we add new changes, it will be important to add regtests for them.  I think that the best way forward is to introduce regtest-only RPC commands that can be used to set the desired fork heights.  This is more flexible than just hardcoding lower heights, for instance, so that tests can decide for themselves how many blocks they need with each fork active.

I'll work on that at some point in the future, but that's also low priority for me right now - but pull requests are welcome if someone wants to do it.  Otherwise you can just edit src/consensus/params.h and hardcode your own fork heights in regtest mode as you need them.

5
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 23, 2016, 06:31:51 PM »
For -regtest, the RPC port changes.  You can set it with -rpcport as well when starting the daemon, if you want.  The default is 18499.

6
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 23, 2016, 01:23:08 PM »
You can use "generate" instead of "setgenerate" to mine.  Even better, use the -regtest mode - there you need only a single daemon (not two connected to each other) and can say "generate 10" to almost immediately mine 10 blocks.

7
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 22, 2016, 05:41:04 PM »
there was an improper shutdown. I over-clocked my miners too much and my PC froze.

I rebooted and restarted the client

before the crash it was synced up to 1192319 blocks

after reboot it's been stuck on activating best chain.. checking the debug log, it's seems to be re-syncing from block 941343 although the qt client just shows the splash screen.

In general, crashing the daemon may corrupt your chain directory - I don't think there's anything specific we can do about that, and it is not Huntercoin-related.  There are regular complaints for Bitcoin as well, and it also happened to me in Bitcoin.  So if anything, we should try to persuade the upstream Bitcoin developers to fix the issue.  The best advice, however, is to keep backups of the chain directory.

8
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 21, 2016, 06:27:52 PM »
Also, thanks all for testing!  If you are syncing from scratch, be aware that there is an "issue" with headers-first sync that should be fixed in upstream Bitcoin: https://github.com/bitcoin/bitcoin/pull/6821  It rarely shows up for Bitcoin, but is much more severe for merge-mined coins and/or coins with short block times - Huntercoin is both.  If your headers sync seems to be getting slower and slower, you can restart the daemon from time to time to clear up the queue of duplicate headers.  Once you have all headers (run getblockchaininfo), this is no longer a problem and blocks should be processed as quickly as your CPU allows.

9
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 21, 2016, 06:25:03 PM »
I can confirm what snailbrain wrote - the chain is incompatible (and even if legacy Bitcoin might be able to convert the chain format (not sure), it most probably won't work for the game-related stuff, so you have to sync fresh).  The wallet should work, and did for me in my own tests (and with my own real wallet.)

10
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 19, 2016, 07:23:30 PM »
It seems obvious from the error that the problem is related to the scrypt code - but I've no detailed knowledge about that, since I've just copied it from the old client.  Any hints would be very appreciated. ;)  It works perfectly on Debian Jessie for me.

11
Development / Re: [ANN] Huntercoin Core - ready for first testing
« on: April 18, 2016, 01:29:21 PM »
You can find my latest source at https://github.com/domob1812/huntercore.  Snailbrain reported issues compiling for Windows, which I unfortunately cannot reproduce on GNU/Linux.  It works fine for me on Debian.


Code: [Select]
rpc/misc.cpp:486:61: error: call of overloaded Pair(const char [8], std::map<std::basic_string<char>, PlayerState>::size_type) is ambiguous
   game.push_back (Pair ("players", gameState.players.size ()));
                                                             ^

The error wasn't there a few weeks ago on the same machine (mint 17.3 32bit VM, nothing installed but dependencies to build Bitcoin + Huntercoin)

using
./configure CPPFLAGS="-msse2" --with-incompatible-bdb
but the CPPFLAGS="-msse2" requirement is probably only scrypt related.

Thanks for testing, should be fixed now.  The error did not show up on my system (Debian Jessie amd64).

12
Development / [ANN] Huntercoin Core - ready for first testing
« on: April 16, 2016, 06:26:05 PM »
After quite a long time, I think that Huntercoin Core is now ready for first "real" testing on mainnet, if you are brave enough.  I've done some tests with the character "domob", and all seemed to be working so far.  The client should be ready for playing (command-line only, so as a backend for something like Mithril or Unity), but do not use it for mining.  That will come later.  Also, of course, there may be severe bugs left that could lead to loss of coins in the extreme.

You can find my latest source at https://github.com/domob1812/huntercore.  Snailbrain reported issues compiling for Windows, which I unfortunately cannot reproduce on GNU/Linux.  It works fine for me on Debian.  Feel free to play around, and if you are able to fix the Windows issues, I'm sure snailbrain can put up a bounty for that from the development funds.

13
General Discussion / Re: Huntercoin 1.3.01 >> Download and info
« on: March 28, 2016, 03:54:00 PM »
It's been a while, but I've just updated the blockchain download at chain.huntercoin.org.

14
Looks good, although I have not checked the VPN configuration steps (I've never worked with OpenVPN myself), so I can't vouch for the security of these.  Three random notes:

1) You can use "nano" instead of "vim" to edit the text files.  While I personally love vim, nano is more similar to ordinary editors and may be easier to use if you do not yet know vim.

2) If you are feeling fancy, consider replacing your SSH root password by SSH pubkey authentication to improve security.

3) In theory, it should not even be necessary to choose a supersecret huntercoin.conf password - the RPC only listens locally, so that no external attacker can access the daemon unless they break your VPN.  It can not hurt, though, and is good advice in general.  You can even set up RPC over TLS, at least if that's supported by the client.

15
Development / Re: simple change proposal
« on: March 24, 2016, 01:53:13 PM »
I've not thought through the game mechanics, just a tiny technical comment:  Introducing such a change could potentially be a softfork rather than hardfork, although it probably depends on how the max height is encoded.  It doesn't really matter for Huntercoin, anyway.  Also, this is of course very similar to Bitcoin's nLockTime, although with "opposite sign".

Pages: [1] 2 3 ... 18