uralcryptocoin
Sr. Member
Offline
Activity: 1042
Merit: 328
SIGNATURE CREATION by uralcryptocoin
|
|
November 03, 2018, 05:41:27 PM |
|
I see that SUQA growths and develops.
But there are couple issues with SUQA wallet that should be corrected I think: 1. I use SUQA latest win wallet (my OS Win7 x64) and CPU usage is very high (up to 100%). It makes the using of the wallet too inconvenient 2. There is a bug of transaction sum imaging: I sent 256 SUQA and after the confirmation I saw that I sent 269.3 SUQA. I was confused how it could be happened? I checked blockchain and see the sum of 256 SUQA. What??? Did I lost my mind? Then I sent another test transaction and it's sum was correct. After I restarted the wallet and saw that my first transaction was 256 SUQA. I tried to send the third transaction and it also was with wrong sum imaging. It's not critical bug however it's still a bug
|
|
|
|
BTC Bitcoin: A Peer-to-Peer Electronic Cash System BTC A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone.
|
|
|
elr01
Member
Offline
Activity: 238
Merit: 13
|
|
November 03, 2018, 07:13:42 PM |
|
As a reply you may rise an issue on github if you have some trace logs. Personnaly I experienced a baffling behavior after building & stripping on Linux, the first runs gave me no message during a couple of seconds, so I thought the binarie was corrupted, and could not figure how to go further. Today I just gave another try in debug mode ... $ strace /my/home/SUQA-CORE/src/SUQAd ..
...and it appears I just had to wait about 30-60s for the daemon to be ready to listen to the network for the first time. Short: may I suggest you to echo a minimal message during this initialisation ?
|
|
|
|
SUQAFOUNDATION (OP)
Copper Member
Member
Offline
Activity: 238
Merit: 11
|
|
November 03, 2018, 08:24:17 PM |
|
|
|
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
November 04, 2018, 08:44:07 AM |
|
I see that SUQA growths and develops.
But there are couple issues with SUQA wallet that should be corrected I think: 1. I use SUQA latest win wallet (my OS Win7 x64) and CPU usage is very high (up to 100%). It makes the using of the wallet too inconvenient 2. There is a bug of transaction sum imaging: I sent 256 SUQA and after the confirmation I saw that I sent 269.3 SUQA. I was confused how it could be happened? I checked blockchain and see the sum of 256 SUQA. What??? Did I lost my mind? Then I sent another test transaction and it's sum was correct. After I restarted the wallet and saw that my first transaction was 256 SUQA. I tried to send the third transaction and it also was with wrong sum imaging. It's not critical bug however it's still a bug
There's a visual bug where the change is counted as fee before the tx is confirmed. Will be fixed in the next release.
|
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
November 04, 2018, 08:44:54 AM |
|
As a reply you may rise an issue on github if you have some trace logs. Personnaly I experienced a baffling behavior after building & stripping on Linux, the first runs gave me no message during a couple of seconds, so I thought the binarie was corrupted, and could not figure how to go further. Today I just gave another try in debug mode ... $ strace /my/home/SUQA-CORE/src/SUQAd ..
...and it appears I just had to wait about 30-60s for the daemon to be ready to listen to the network for the first time. Short: may I suggest you to echo a minimal message during this initialisation ? The dalay is before the first line of code is executed :-)
|
|
|
|
cccomputing
Jr. Member
Offline
Activity: 34
Merit: 2
|
|
November 04, 2018, 10:32:46 AM |
|
Any good pool suggestions? Icemining is down on any stratum for me and beepool only recognizes 60Mh or 500Mh. F2Pool? I dont like the 3% fee
|
|
|
|
lupinjhon
Newbie
Offline
Activity: 56
Merit: 0
|
|
November 04, 2018, 10:43:42 AM |
|
Ok we have SUQA, now we need only BLYAT coin.
|
|
|
|
KarlSQ
Newbie
Offline
Activity: 22
Merit: 0
|
|
November 04, 2018, 10:45:57 AM |
|
Any good pool suggestions? Icemining is down on any stratum for me and beepool only recognizes 60Mh or 500Mh. F2Pool? I dont like the 3% fee
I use bsod (0.9% fee)
|
|
|
|
cccomputing
Jr. Member
Offline
Activity: 34
Merit: 2
|
|
November 04, 2018, 10:46:43 AM |
|
But bsod.pw is a Solo only pool right? I dont have a Party to mine with or how i just use it as a regular pool with pps or pplns or something?
|
|
|
|
XXII
Newbie
Offline
Activity: 2
Merit: 0
|
|
November 04, 2018, 10:57:45 AM |
|
But bsod.pw is a Solo only pool right?
It's a regular pool for the 0.9% fee. Additionally they also offer a solo and a "party" option for private groups with a 1.9% fee. (port for SUQA is 2460) Europe server:-o stratum+tcp://eu.bsod.pw:<PORT> -u <WALLET_ADDRESS> [-p <OPTIONS>] North America server:-o stratum+tcp://us.bsod.pw:<PORT> -u <WALLET_ADDRESS> [-p <OPTIONS>] Asia server:-o stratum+tcp://asia.bsod.pw:<PORT> -u <WALLET_ADDRESS> [-p <OPTIONS>] SOLO mining:m=solo in password field ("-p m=solo"), so it would look like this: -a algo -o stratum+tcp://eu.bsod.pw:PORT -u WALLET.rig -p m=solo PARTY mining:m=party.YOUR_PARTY_PASSWORD in password field, so it would look like this: -a algo -o stratum+tcp://eu.bsod.pw:PORT -u WALLET.rig -p m=party.YOUR_PARTY_PASSWORD Edit: added server options
|
|
|
|
SUQAFOUNDATION (OP)
Copper Member
Member
Offline
Activity: 238
Merit: 11
|
|
November 04, 2018, 11:51:58 AM |
|
Please swap all your SUQA to SUQA Coin from the link below. First click on the right below side where it is showing in red 1.000 with 2.4 million sell orders once and then click on the middle left to how much SUQA you have and then click buy. Please do this ASAP as this is the only process left to merge the pairs and volumes in escodex. https://wallet.escodex.com/market/ESCODEX.SUQACOIN_ESCODEX.SUQA
|
|
|
|
cccomputing
Jr. Member
Offline
Activity: 34
Merit: 2
|
|
November 04, 2018, 12:00:37 PM |
|
Please swap all your SUQA to SUQA Coin from the link below.
What? Why? Didnt read anything about that yet!
|
|
|
|
fosograf
|
|
November 04, 2018, 12:53:43 PM |
|
Ok we have SUQA, now we need only BLYAT coin.
Tы тaкoй opигинaльный) Пpям вaщe никтo нe шyтил кaк ты, caдиcьпять
|
|
|
|
XXII
Newbie
Offline
Activity: 2
Merit: 0
|
|
November 04, 2018, 12:54:15 PM |
|
Please swap all your SUQA to SUQA Coin from the link below.
I figure this only applies to coins that were transfered to escodex, right?
|
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
November 04, 2018, 01:21:55 PM |
|
Please swap all your SUQA to SUQA Coin from the link below.
I figure this only applies to coins that were transfered to escodex, right? Yes. Coins deposited on the obsolete symbol SUQA. Now SUQACOIN must be used. They had to dispose of the old one because it was misconfigured on their side.
|
|
|
|
Newminer2018
Newbie
Offline
Activity: 29
Merit: 0
Just mining for fun
|
|
November 04, 2018, 01:22:53 PM |
|
Any good pool suggestions? Icemining is down on any stratum for me and beepool only recognizes 60Mh or 500Mh. F2Pool? I dont like the 3% fee
I use bsod (0.9% fee) Can you tell me what your batch file is as my miners will and have not connected to BSOD and when I try to lookup the pool, i get cannot open page so thought it was down.
|
|
|
|
fofofofo
Newbie
Offline
Activity: 3
Merit: 0
|
|
November 04, 2018, 01:45:57 PM |
|
Any good pool suggestions? Icemining is down on any stratum for me and beepool only recognizes 60Mh or 500Mh. F2Pool? I dont like the 3% fee
I use bsod (0.9% fee) Can you tell me what your batch file is as my miners will and have not connected to BSOD and when I try to lookup the pool, i get cannot open page so thought it was down. @echo off :start t-rex -a x22i -o stratum+tcp://eu.bsod.pw:2460 -u WALLETADDRESS.miner1 -p c=SUQA -i 20 goto start
|
|
|
|
boba022
Jr. Member
Offline
Activity: 44
Merit: 1
|
|
November 04, 2018, 02:40:29 PM |
|
Please swap all your SUQA to SUQA Coin from the link below.
What? Why? Didnt read anything about that yet! I guess it only applies to SUQA coins deposited to ESCODEX exchange.
|
|
|
|
Newminer2018
Newbie
Offline
Activity: 29
Merit: 0
Just mining for fun
|
|
November 04, 2018, 03:02:03 PM |
|
Any good pool suggestions? Icemining is down on any stratum for me and beepool only recognizes 60Mh or 500Mh. F2Pool? I dont like the 3% fee
I use bsod (0.9% fee) Can you tell me what your batch file is as my miners will and have not connected to BSOD and when I try to lookup the pool, i get cannot open page so thought it was down. @echo off :start t-rex -a x22i -o stratum+tcp://eu.bsod.pw:2460 -u WALLETADDRESS.miner1 -p c=SUQA -i 20 goto start
Many thanks.
|
|
|
|
|