I read the whitepaper, more than once, and I also agree that there is no actual gameplay and this is a pyramid scheme. Unless you consider buying out other tiles to maximize your influence as gameplay. But that's only true when the land plots you need to buy are actually put up for sale...

Thanks for the reply, but there is still something I don't fully understand... the node accepts HTTP and RPC requests during regular operation, from other nodes in the network? This means anyone can spam my IP with these sort of requests to bring the node down?

I'm getting this error message on a VPS node that I am not using for RPC calls. It's just online and I don't do anything else than let it run.


.conf is set to rpcallowip=127.0.0.1 so no outside RPC calls are allowed.

The node stops working when this happens and resumes normally after a reboot.

1. What could be triggering this error?
2. What can I do to avoid it? Settings recommended [ DO NOT POST SESC LINKS ]here[/url] fix it or just delay the problem?
3. Is there a log or a command that allows me to query and monitor the number and origin of RPC quests over time?

Que opções são essas, mais rentáveis?

From the Whitepaper, https://espers.io/download/Espers-White-Paper-v1-Final.pdf page 17:

"Instead, X-Nodes are completely opt-in meaning that any community member may participate in the system regardless of their current balance or previous experience."

"A participating user may then also lock any desired amount of their balance which will effectively become frozen as the participant will no longer be able to stake them until they are unlocked from the X-Node and in doing so have the balance act as a multiplier to the compensation rate provided."

You are a bit confused.
You mine ETH, you cannot mine ETH tokens... so makes no sense to have mining pools for tokens...

So trust nodes just create buy pressure and remove coins from circulation to help keep the price up.

... and I guess if the dev team holds a lot of them, it's a way to finance their efforts and reward their hard work if successful.

I can live with this, it's just that if this is the case, the need/importance for trust nodes is a bit exaggerated, it seems to me.

My question is with trust nodes, not escrow nodes...

Escrow nodes needs a person with a brain to actually do some work and monitor the transactions; Trust nodes, you just lock the tokens in the ETH blockchain through a contract and wait for passive income. There is nothing else to do, so what exactly is locking these tokens doing that could not happen without this feature?

Yes, yes, I already read that a few times, the same wording in a few different places.

But what I want to know is exactly how sending tokens to an ETH contract contributes to the "job of maintaining, updating, and securing the PayFair ecosystem".

I was reading your whitepaper, because there is something I don't understand. You say that a 'trust node is a critical element', but what exactly does it do?

Does it run any code in the ETH blockchain to settle transactions? And if it does, why do you need many accounts loaded with tokens and registered to accomplish... whatever the trust nodes are going to accomplish?

Does it provide any other service than an incentive to buy tokens?

From what I could read, it seems to be just a way to keep some buying pressure on the token, much as all those scammy Dash clones popping up every week.

Can we check the txs in a block explorer? I tried the first few in https://kmd.explorer.supernet.org/ but it returns no matching records...

https://imgur.com/a/knUK1

Registration is buggy?

I tested the drivers in Ubuntu 16.04.3, from http://support.amd.com/en-us/kb-articles/Pages/AMDGPU-Pro-Beta-Mining-Driver-for-Linux-Release-Notes.aspx
The test GPU was a Radeon R9 Fury X, which is listed as compatible.

At first the drivers were breaking boot (tried 2 versions in different AMD support pages), there was no GUI. To uninstall, you can press Ctrl+Alt+F1, login with your credentials and run .

Then I started googling and found https://askubuntu.com/questions/880523/cant-login-after-installing-amdgpu-pro-16-60 other people that were able to get the drivers working by using one of the options of the install script, either
or

Everything else was working as per the official AMD support pages.

I'm trying to figure out if the latest version is compatible with R9 Fury X cards. OP mentions "1. Install Catalyst v15.12 for old AMD cards; for Fury, Polaris and Vega cards use latest blockchain drivers." and then "This version is for recent AMD videocards only: 7xxx, 2xx and 3xx, 2GB or more."

First, what are "blockchain drivers"? Was this a mistake? It seems that Fury is ok from this part, but then this card is not included in the "recent AMD videocards only: 7xxx, 2xx and 3xx" group.

Can someone clarify please? Thanks.

I'm not sure... maybe you can ask someone in Slack? I for one still haven't received any bytes yet.

If you're fast and the snapshot didn't happen yet, you may still be able to fix the issue.

Did you move any coins, even a small amount, after you last checked the linked balance? If you did, the remaining coins should be in another address in your wallet and you'd need to transfer them back to the linked address.

Payment processing is off, ok, but if you find a block the coins have to go somewhere, and that is a a main address you set up in the NOMP pool or an address generated by the wallet created by komodod? Either way if you're solo mining, payouts feature doesn't matter as long as blocks rewards go to an address you control, correct?

1% of KMD not sure how much that amounts to. How many blocks is that in 24h on average and roughly how many coins for the same period?

Thanks.

There are people doing arbitrage all the time, which means that BTCD price will closely follow KMD because if BTCD falls behind too much there is profit to be made by bringing the values closer together.

I have a wallet file created with the GUI client 1.0.9. That wallet file doesn't seem to work with the reference client 2.0.0. Can anyone confirm this? I even changed the wallet's password to avoid special characters. I can open a new wallet created in 2.0.0.

I'm not in a hurry to move the coins. If I wait for GUI 2.0.0, will this be fixed? Or should I just send all the coins to an exchange from the 1.0.9 wallet and then send it to a new 2.0.0 wallet?

Also, this 2.0.0 wallet is creating the wallet file in the program directory instead of the (usual) ~/.bytecoin location.

There are 2 repositories (that I know of) for the Blitz wallet:
- The one posted in ANN here (https://bitcointalk.org/index.php?topic=848186.0): https://bitbucket.org/blitz-dev/blitz-public
- Another one used for the Azure submission: https://github.com/KemBits/blitz-coin

I cannot run the qt wallet or the daemon and I get the same problems with both repositories. The system runs on Lubuntu 15.10.
Lubuntu currently installs Boost 1.58, where wallet docs indicate 1.37.
I have berkeleydb 4.8 installed from bitcoin ppa, and also the most recent version that comes with Lubuntu. Apt-get tells me I should remove the 2 packages for 4.8...

While compiling the Qt wallet, I get this error (I left everything at defaults, upnp etc when issuing qmake):
g++: error: /usr/local/src/blitz/src/leveldb/libleveldb.a: No such file or directory
g++: error: /usr/local/src/blitz/src/leveldb/libmemenv.a: No such file or directory
Makefile:810: recipe for target 'blitz-qt' failed
make: *** [blitz-qt] Error 1

Those 2 files do not exist and are in fact listed in .gitignore, in the folder they were supposed to be in.
I don't know if this is related, but /src/leveldb/build_detect_platform already comes with execute permissions (at least when cloned from the bitbucket repo).
I solved this part by following this post: https://bitcointalk.org/index.php?topic=260031.msg2774736#msg2774736
Basically I compile the 2 missing files before the 'main' qmake/make:

After this problem goes away, I get a few Boost errors:
/usr/bin/ld: cannot find -lboost_system-mt
/usr/bin/ld: cannot find -lboost_filesystem-mt
/usr/bin/ld: cannot find -lboost_program_options-mt
/usr/bin/ld: cannot find -lboost_thread-mt
/usr/bin/ld: cannot find -lboost_date_time-mt
/usr/bin/ld: cannot find -lboost_chrono-mt
collect2: error: ld returned 1 exit status
Makefile:804: recipe for target 'blitz-qt' failed
make: *** [blitz-qt] Error 1

And according to this http://askubuntu.com/questions/486006/cannot-find-boost-thread-mt-library
The mt (multithreading) has been removed and is not needed any more. Fixes are: either update the code or symlink to the correct (-mt less) files. I created all the symlinks and make finally completed successfully.

Then at run time, execution was halted (its a VNC session):

./blitz-qt
Qt: XKEYBOARD extension not present on the X server.
QGradient::setColorAt: Color position must be specified in the range 0 to 1
QGradient::setColorAt: Color position must be specified in the range 0 to 1
Abr 26 20:46:12.469 [err] tor_assertion_failed_(): Bug: src/tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting.
Abr 26 20:46:12.500 [err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at src/tor/memarea.c:127. Stack trace:
Abr 26 20:46:12.500 [err] Bug:     ./blitz-qt() [0x8114e63]
Abr 26 20:46:12.500 [err] Bug:     ./blitz-qt() [0x81fa050]
Abr 26 20:46:12.500 [err] Bug:     ./blitz-qt() [0x81a7d8c]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81a7e67]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81f21c5]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81bdc69]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81bddf5]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81be165]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81be3ca]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x814590f]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x814a73d]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x814aa6f]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81b83fd]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x81b9436]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x82e2af7]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt(_Z12ThreadTorNetPv+0x3f) [0x82e2bef]
Abr 26 20:46:12.501 [err] Bug:     ./blitz-qt() [0x8268b80]
Abr 26 20:46:12.501 [err] Bug:     /usr/lib/i386-linux-gnu/libboost_thread.so.1.58.0(+0xdc05) [0xb71eac05]
Abr 26 20:46:12.501 [err] Bug:     /lib/i386-linux-gnu/libpthread.so.0(+0x61aa) [0xb368c1aa]
Abr 26 20:46:12.501 [err] Bug:     /lib/i386-linux-gnu/libc.so.6(clone+0x5e) [0xb33d202e]
Aborted (core dumped)

At this point I'm stuck and I cannot find any solutions searching in Google. Is this a Boost update problem, something about the Tor code, something wrong with my Boost installation or is it something else?

Regarding the daemon, I was able to compile, but then I also got runtime errors:
/usr/local/src/blitz/src$ ./blitzd
Apr 18 03:33:50.855 [err] tor_assertion_failed_(): Bug: tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting.
Apr 18 03:33:50.873 [err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at tor/memarea.c:127. Stack trace:
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x825ea5e]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x83443ba]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x82f01a6]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x82f0278]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x83372ee]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x8306a54]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x8306bc7]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x8306ee8]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x830711e]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x828f979]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x82944f1]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x829481a]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x830127f]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x83022cc]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x81732df]
Apr 18 03:33:50.873 [err] Bug:     ./blitzd() [0x81733be]
Apr 18 03:33:50.873 [err] Bug:     /usr/lib/i386-linux-gnu/libboost_thread.so.1.58.0(+0xdc05) [0xb76a5c05]
Apr 18 03:33:50.873 [err] Bug:     /lib/i386-linux-gnu/libpthread.so.0(+0x61aa) [0xb71ea1aa]
Apr 18 03:33:50.873 [err] Bug:     /lib/i386-linux-gnu/libc.so.6(clone+0x5e) [0xb6f2102e]
Aborted (core dumped)

The runtime problem seems to be quite similar in every case.
Has anyone been able to compile and run this in Ubuntu recently?