tomsmith26
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 19, 2016, 10:53:48 PM |
|
I love this coin . it looks nice and bright.
Just ask When the POW can mine?
|
|
|
|
Cryptco
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 19, 2016, 11:11:30 PM |
|
I love this coin . it looks nice and bright.
Just ask When the POW can mine?
hi tomsmith26. POW mining is over- POS only. 2 day Minimum Stake age 14 day Maximum Stake age POS, 30 Coins per Block
|
|
|
|
RiotMachine
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 80
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 19, 2016, 11:14:53 PM Last edit: July 20, 2016, 04:26:59 AM by RiotMachine |
|
Great new OP, I hope the new wallet doesn't use so much network bandwidth, that was the reason I never kept the old wallet open. I will multisend 50% as soon as the new wallet is open until we reach our goal. Edit: New wallet is absolutely beautiful, great work, multisend is now at 50%.
Edit2: The blockchain is now synced with the new wallet, and it still continues to use 1 Mbps / 128 KBps, I can't use my internet hardly while the wallet is open, if anybody could offer a fix that would be great, until then I'll have to keep the new beautiful wallet closed :/
|
|
|
|
AmoreJaz
Legendary
Offline
Activity: 3220
Merit: 1103
Leading Crypto Sports Betting & Casino Platform
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 19, 2016, 11:55:56 PM |
|
i will compile this and check it out and hopefully it isnt a resourse hog like the previous version. having a few wallets all running and staking on the same computer is easy if the wallets play nice together but having to dedicate a single machine to a single wallet like before just isnt practical thanks for the hard work and keep up the innovations! Cheers
|
..Stake.com.. | | | ▄████████████████████████████████████▄ ██ ▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄ ██ ▄████▄ ██ ▀▀▀▀▀▀▀▀▀▀ ██████████ ▀▀▀▀▀▀▀▀▀▀ ██ ██████ ██ ██████████ ██ ██ ██████████ ██ ▀██▀ ██ ██ ██ ██████ ██ ██ ██ ██ ██ ██ ██████ ██ █████ ███ ██████ ██ ████▄ ██ ██ █████ ███ ████ ████ █████ ███ ████████ ██ ████ ████ ██████████ ████ ████ ████▀ ██ ██████████ ▄▄▄▄▄▄▄▄▄▄ ██████████ ██ ██ ▀▀▀▀▀▀▀▀▀▀ ██ ▀█████████▀ ▄████████████▄ ▀█████████▀ ▄▄▄▄▄▄▄▄▄▄▄▄███ ██ ██ ███▄▄▄▄▄▄▄▄▄▄▄▄ ██████████████████████████████████████████ | | | | | | ▄▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ ▄▀▄ █▀▀█▀▄▄ █ █▀█ █ ▐ ▐▌ █ ▄██▄ █ ▌ █ █ ▄██████▄ █ ▌ ▐▌ █ ██████████ █ ▐ █ █ ▐██████████▌ █ ▐ ▐▌ █ ▀▀██████▀▀ █ ▌ █ █ ▄▄▄██▄▄▄ █ ▌▐▌ █ █▐ █ █ █▐▐▌ █ █▐█ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀█ | | | | | | ▄▄█████████▄▄ ▄██▀▀▀▀█████▀▀▀▀██▄ ▄█▀ ▐█▌ ▀█▄ ██ ▐█▌ ██ ████▄ ▄█████▄ ▄████ ████████▄███████████▄████████ ███▀ █████████████ ▀███ ██ ███████████ ██ ▀█▄ █████████ ▄█▀ ▀█▄ ▄██▀▀▀▀▀▀▀██▄ ▄▄▄█▀ ▀███████ ███████▀ ▀█████▄ ▄█████▀ ▀▀▀███▄▄▄███▀▀▀ | | | ..PLAY NOW.. |
|
|
|
wdl1908
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 12:09:19 PM |
|
Does anyone have a recent nodelist
|
|
|
|
vancefox
Legendary
Offline
Activity: 1033
Merit: 1005
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 12:23:59 PM |
|
Broken already... outstanding...
|
This space not for rent...
|
|
|
wdl1908
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 12:39:25 PM |
|
Compiled it on a 32 bit debian install when I get through the one fatal compile error and start it it gives me this. Jul 20 14:35:55.454 [err] tor_assertion_failed_(): Bug: src/tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting. Jul 20 14:35:55.455 [err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at src/tor/memarea.c:127. the compile error is in net.ccp line 65 should be boost::array<int, THREAD_MAX> vnThreadsRunning; instead of array<int, THREAD_MAX> vnThreadsRunning; I had to upgrade boost to version 1.6 else it would not compile due to SSL3 not compiling. Please provide a pre-compiled 32 bit linux version.
|
|
|
|
wdl1908
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 12:53:01 PM |
|
Nice whoever incorporated this tor stuff just dumped a preconfigured source for 64 bit in there without even considering that some people would like to run it on w 32 bit system.
Please get rid of the tor stuff it only gets in the way of good staking. The latency is too much for a staking coin.
|
|
|
|
PayCon (CON) (OP)
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 96
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 01:13:33 PM |
|
Thank you for pointing out the potential bug for us, we will look into it. Also, we did not incorporate TOR it was already part of the coin when we came in. We will be switching CON to a completely new code base and at that point it will no longer have TOR. We appreciate your concerns and will try to get pre-compiled 32bit Linux wallet up for you today.
|
|
|
|
wdl1908
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 01:19:22 PM |
|
You made a new git repo with an initial commit why?
It would be better to fork the existing repo and then make changes to that so people would know the code could be trusted and see all the changes you have made to the original code.
Just a suggest to increase the trust level of a new OP.
|
|
|
|
isamamin
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 263
Merit: 250
semux
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 01:24:50 PM |
|
pool?
|
|
|
|
grajson
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 100
Merit: 11
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 01:25:58 PM |
|
Any bounties for translations of the OP? I can do Polish translation. PM sent @PayCon (CON)
|
|
|
|
|
RiotMachine
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 80
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 03:42:48 PM |
|
Thank you for pointing out the potential bug for us, we will look into it. Also, we did not incorporate TOR it was already part of the coin when we came in. We will be switching CON to a completely new code base and at that point it will no longer have TOR. We appreciate your concerns and will try to get pre-compiled 32bit Linux wallet up for you today.
Thank you for the quick reply, is there an estimate for when the new code will be completed?
|
|
|
|
AngelLox
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 07:05:10 PM |
|
Compiled it on a 32 bit debian install when I get through the one fatal compile error and start it it gives me this. Jul 20 14:35:55.454 [err] tor_assertion_failed_(): Bug: src/tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting. Jul 20 14:35:55.455 [err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at src/tor/memarea.c:127. the compile error is in net.ccp line 65 should be boost::array<int, THREAD_MAX> vnThreadsRunning; instead of array<int, THREAD_MAX> vnThreadsRunning; I had to upgrade boost to version 1.6 else it would not compile due to SSL3 not compiling. Please provide a pre-compiled 32 bit linux version. Nice whoever incorporated this tor stuff just dumped a preconfigured source for 64 bit in there without even considering that some people would like to run it on w 32 bit system.
Please get rid of the tor stuff it only gets in the way of good staking. The latency is too much for a staking coin.
I can tell you that when i had a pi2 (32 bit arch) i couldn't compile the wallet and i came to the conclusion that the tor stuff didn't run on 32 bit arch There are plans to remove tor as soon as the next update.
|
|
|
|
wdl1908
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 20, 2016, 10:09:23 PM |
|
Compiled it on a 32 bit debian install when I get through the one fatal compile error and start it it gives me this. Jul 20 14:35:55.454 [err] tor_assertion_failed_(): Bug: src/tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting. Jul 20 14:35:55.455 [err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at src/tor/memarea.c:127. the compile error is in net.ccp line 65 should be boost::array<int, THREAD_MAX> vnThreadsRunning; instead of array<int, THREAD_MAX> vnThreadsRunning; I had to upgrade boost to version 1.6 else it would not compile due to SSL3 not compiling. Please provide a pre-compiled 32 bit linux version. Nice whoever incorporated this tor stuff just dumped a preconfigured source for 64 bit in there without even considering that some people would like to run it on w 32 bit system.
Please get rid of the tor stuff it only gets in the way of good staking. The latency is too much for a staking coin.
I can tell you that when i had a pi2 (32 bit arch) i couldn't compile the wallet and i came to the conclusion that the tor stuff didn't run on 32 bit arch There are plans to remove tor as soon as the next update. Oh it does run on 32 bit but you need to fiddle a bit with the config. file src/tor/orconfig_linux.h line 537
|
|
|
|
wdl1908
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 21, 2016, 10:25:17 AM Last edit: July 21, 2016, 11:02:41 AM by wdl1908 |
|
Well no joy on the 32 bit front. the program ran once with an empty dabaase dir but when restarrting it refuses to run and stops without an error message.
Edit: After removing the tor and onion dirs in the .PayCon dir the program starts so it has something to do with the saved information about tor.
|
|
|
|
CON_CEO
Newbie
Offline
Activity: 8
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2016, 12:31:12 AM |
|
Well no joy on the 32 bit front. the program ran once with an empty dabaase dir but when restarrting it refuses to run and stops without an error message.
Edit: After removing the tor and onion dirs in the .PayCon dir the program starts so it has something to do with the saved information about tor.
There was a no-tor branch in the crestington repo which was for 32 bit and worked along side the tor
|
|
|
|
cryptotech
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2016, 01:34:01 AM Last edit: July 22, 2016, 05:22:38 AM by cryptotech |
|
Well no joy on the 32 bit front. the program ran once with an empty dabaase dir but when restarrting it refuses to run and stops without an error message.
Edit: After removing the tor and onion dirs in the .PayCon dir the program starts so it has something to do with the saved information about tor.
There was a no-tor branch in the crestington repo which was for 32 bit and worked along side the tor Hello crest! Like speaking about yourself in the third person? lol Your repo might have that branch but it will not work along side the new code unless I add in the new changes made as the new wallet is a mandatory update which will Hardfork at block 800k. I will look into it. @Wdl1908 I built the 32bit wallet and I'm also getting the exact same issue. Works on first launch then the errors unless I delete onion and TOR folders I will continue to try my best to work the issue you out though. Let me know if you find a fix as well. Thanks The new code base will not have TOR and we will not have to worry about these issues any more.
|
|
|
|
wdl1908
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 22, 2016, 07:59:52 AM |
|
Well at the moment I can live with the erase before start stuff. And the wallet seems to stake ok.
|
|
|
|
|