[HXX SWAP] |HexxCoin| CPU | Anonymous Zerocoin | C-CEX | Yobit | Cryptopia |

[shiki0]

when swap will be end ?

Swap has ended, HEXX is in the process of taking over, new SITE / WP / ANN

STAY TUNED

Is there a second swap in addition to the one noted in the ANN or can i just reuse my wallet.dat from a few months ago?

Also are the requirements for znodes the same as for zcoin (1000 HXX)?

No more SWAPS, just a core update once the DEV completes the Xnodes

Requirements not yet set, do note that supply of HXX is atm ~1.5mil and XZC ~4mil

[1715084081]

1715084081

[1715084081]

1715084081

[1715084081]

1715084081

[shiki0]

Your old wallet.dat will work!
Please use the latest wallet version -> https://github.com/hexxcointakeover/4.0.1.X

[felixbrucker]

Thanks, done that

I have some 500-ish HXX leftover. Thought about setting up a masternode with them but probably need to get some HXX from exchanges.

[wasabi.domo]

Just jumped onto channels to see what the community was like. It's small but growing. Exciting too see. I'm hoping this coin can get back on its feet. Great to see the reboot.

[felixbrucker]

Found the part in the code (https://github.com/hexxcointakeover/4.0.1.X/blob/master/src/znode.h#L25) though it is currently 10 for testing it previously was 1000, will need to wait for dev to make the final decision on how many hxx are required

[Slkp]

win64 beta 4.0.1.4 wallet:

https://github.com/hexxcointakeover/4.0.1.X/releases/tag/4.0.1.4

please stop using 3.x.x.x wallets

why?If it work too

[shiki0]

Global hashrate went x5, price also spiked 

[Ned Kelly]

win64 beta 4.0.1.4 wallet:

https://github.com/hexxcointakeover/4.0.1.X/releases/tag/4.0.1.4

please stop using 3.x.x.x wallets

why?If it work too

You need a client which has support for forthcoming upgrade.

[felixbrucker]

It seems in the current wallet (4.0.1.4) RPC doesn't work? Postman shows "error connecting to .."

[ngockhue072]

New pool HXX

http://dpool.co

Use your wallet address as your username, and c=HXX as your password.
No registration required.

Can be tested with

Code:

-a lyra2z330 -o stratum+tcp://dpool.co:4555 -u H7aZZZR1VgwCktTYrpswp6S8Q3C7htaJZ6 -p c=HXX   
pause

[shiki0]

New pool HXX

http://dpool.co

Use your wallet address as your username, and c=HXX as your password.
No registration required.

Can be tested with

Code:

-a lyra2z330 -o stratum+tcp://dpool.co:4555 -u H7aZZZR1VgwCktTYrpswp6S8Q3C7htaJZ6 -p c=HXX   
pause

COOL, mining difficulty x10 in 3 days 

...will the price catch up

[ngockhue072]

New pool HXX

http://dpool.co

Use your wallet address as your username, and c=HXX as your password.
No registration required.

Can be tested with

Code:

-a lyra2z330 -o stratum+tcp://dpool.co:4555 -u H7aZZZR1VgwCktTYrpswp6S8Q3C7htaJZ6 -p c=HXX   
pause

COOL, mining difficulty x10 in 3 days 

...will the price catch up

Whose pool?

[shiki0]

It seems in the current wallet (4.0.1.4) RPC doesn't work? Postman shows "error connecting to .."

use QT version to get the RPC up...

[felixbrucker]

It seems in the current wallet (4.0.1.4) RPC doesn't work? Postman shows "error connecting to .."

use QT version to get the RPC up...

I am using the qt version. My config is as follows, maybe i missed something?

Code:

rpcport=12345
rpcpassword=test
rpcuser=test
rpcbind=0.0.0.0
rpcallowip=127.0.0.0/8
server=1

[shiki0]

It seems in the current wallet (4.0.1.4) RPC doesn't work? Postman shows "error connecting to .."

use QT version to get the RPC up...

I am using the qt version. My config is as follows, maybe i missed something?

Code:

rpcport=12345
rpcpassword=test
rpcuser=test
rpcbind=0.0.0.0
rpcallowip=127.0.0.0/8
server=1

./hexxcoin-qt -server -rpcuser=xxx -rpcpassword=xxx -rpcallowip=0.0.0.0/0 -rpcthreads=100 &

works for me!

[felixbrucker]

Doesn't work for me unfortunately

I'm using the windows release so that might be the cause?

[felixbrucker]

I checked further and it seems:

- the wallet listens correctly on the specified port and authentication works
- the wallet doesn't send the correct content length in its response (HPE_INVALID_CONTENT_LENGTH)
- happens with beta2 wallet as well

Somebody knows why that might be?

Edit: Wireshark confirmed that, the content length field contains invalid input (characters 'zu\r\n'):



Also it seems always to be 'zu\r\n', regardless of the methods used and if they throw an error like "method not found"

Edit: Also just found this, might be the cause that the windows wallet is compiled with an very old version of visual studio: https://stackoverflow.com/questions/15610053/correct-printf-format-specifier-for-size-t-zu-or-iu

[Asimmo]

What I do know is that development is in safe hands.
Stay tuned by the end of this month..

[hexxodev_temp]

I checked further and it seems:

- the wallet listens correctly on the specified port and authentication works
- the wallet doesn't send the correct content length in its response (HPE_INVALID_CONTENT_LENGTH)
- happens with beta2 wallet as well

Somebody knows why that might be?

Edit: Wireshark confirmed that, the content length field contains invalid input (characters 'zu\r\n'):



Also it seems always to be 'zu\r\n', regardless of the methods used and if they throw an error like "method not found"

Edit: Also just found this, might be the cause that the windows wallet is compiled with an very old version of visual studio: https://stackoverflow.com/questions/15610053/correct-printf-format-specifier-for-size-t-zu-or-iu

will get on it later.
compiled with ubuntu 18

[felixbrucker]

will get on it later.
compiled with ubuntu 18

then it probably can be solved with this: https://stackoverflow.com/questions/44382862/how-to-printf-a-size-t-without-warning-in-mingw-w64-gcc-7-1

hope it helps