Bitcoin Forum
May 23, 2024, 10:47:14 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 [172] 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 »
  Print  
Author Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer!  (Read 284891 times)
a123
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
July 19, 2014, 09:25:01 PM
 #3421

For the 100th time, THERE IS A BLOCK PROPAGATION ISSUE WITH THE WALLET! IT GOES OUT OF SYNC EVERY COUPLE OF HOURS.

At this very moment i have 15 wallets open (same wallet.dat file, compiled using latest code from github)
1 hour ago i burned 200 slims. Only 3 wallets out of 15 showed the updated balance. It took the other 12 wallets 24 minutes to show updated balance.

While troubleshooting the issue, i tried sending 1slm from one of the stuck wallets. As soon as I broadcasted the transaction it started syncing. This explains why sandors pool wallet has no sync issues, it has a constant flux of incoming and outgoing transactions.



Good discovery. I have been getting an orphan rate of around 20% for PoW which has been rather annoying.

I'll have a script monitor the pools and send SLMs around once my block gets stuck; will update if this works.
d5000
Legendary
*
Offline Offline

Activity: 3920
Merit: 6360


Decentralization Maximalist


View Profile
July 20, 2014, 03:34:06 AM
 #3422

I have a problem installing the Linux executable from Github. When I download slimcoin-linux.tar.gz, untar it and try to start it I get the following error:

Code:
-bash: ./slimcoind: cannot execute binary file: Exec format error

I tried it on two different machines (home PC and VPS), same problem. What am I doing wrong, or is this a bug?

(PS: Please, rename the slicmoin-executable directory. It looks terrible.)

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
slimcoin (OP)
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile WWW
July 20, 2014, 04:28:08 AM
 #3423

The linux binaries are not perfect yet. I am working on getting statically linked 32 and 64 bit binaries. Currently, they are dynamically linked for 64 bit. It is best for you to just download all of the libraries and compile it yourself. Compiling on linux is not hard at all, look at build-unix.txt in the doc/ directory.

-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
idad01
Full Member
***
Offline Offline

Activity: 148
Merit: 100


View Profile
July 20, 2014, 05:27:02 AM
 #3424

Why is there a lot of invalid block, I deleted all files except the wallet.dat and began re-start synchronization!
jadefalke
Legendary
*
Offline Offline

Activity: 1457
Merit: 1014


View Profile
July 20, 2014, 07:08:57 AM
 #3425

hi,

when i went to bed Yesterday everything with my Client was ok, now he rolled back a lot of Transactions and they are unconfirmed. Unconfirmed Transaction start 11.07.2014 around 2:51 GMT+1. Does anybody else had such a Problem? How can i Fix that?
Could it be possible that we have a Fork issue again, or is it only my Client out of sync?
jadefalke
Legendary
*
Offline Offline

Activity: 1457
Merit: 1014


View Profile
July 20, 2014, 07:10:50 AM
 #3426

a second node has the same Problem and is also on a Fork. looks like it's a Problem in general.
d5000
Legendary
*
Offline Offline

Activity: 3920
Merit: 6360


Decentralization Maximalist


View Profile
July 20, 2014, 07:19:08 AM
 #3427

The linux binaries are not perfect yet. I am working on getting statically linked 32 and 64 bit binaries. Currently, they are dynamically linked for 64 bit. It is best for you to just download all of the libraries and compile it yourself. Compiling on linux is not hard at all, look at build-unix.txt in the doc/ directory.

Thanks. I tried to compile slimcoind now (using the latest code on git), but compiler (g++ 4.8.2) gets stuck (simply stops to compile) after the following lines:

Code:
main.cpp:994:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   int64 nRewardCoinYear = nTime > POB_POS_TARGET_SWITCH_TIME ? (10 * CENT) : CENT;  // creation amount per coin-year
   ^
main.cpp:1030:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   if(fTestNet || nTime > POB_POS_TARGET_SWITCH_TIME)
   ^
main.cpp:1125:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   if(fTestNet || pindexLast->nTime > POB_POS_TARGET_SWITCH_TIME)
   ^
main.cpp:2380:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   if(fTestNet || GetBlockTime() > CHAINCHECKS_SWITCH_TIME)

Unfortunately there is no version marked as "stable" which I could try.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
ynyjl
Member
**
Offline Offline

Activity: 86
Merit: 10


View Profile
July 20, 2014, 07:34:03 AM
 #3428

Fork blockchain:

long:
getblockhash 35586
000000006012e412c9009be384d2a5686a06949e5b36d1c4b909b955c2fd0033
getblockhash 35587
07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155

short:
getblockhash 35586
000000006012e412c9009be384d2a5686a06949e5b36d1c4b909b955c2fd0033
getblockhash 35587
fc673b277c18d9c7f456610f4ef2f3d93b75ee1028da982b6e373d91b234231c
slimcoin (OP)
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile WWW
July 20, 2014, 07:35:17 AM
 #3429

That fork will be fixed through the syncronized checkpoints

-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
slimcoin (OP)
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile WWW
July 20, 2014, 07:37:11 AM
 #3430

The linux binaries are not perfect yet. I am working on getting statically linked 32 and 64 bit binaries. Currently, they are dynamically linked for 64 bit. It is best for you to just download all of the libraries and compile it yourself. Compiling on linux is not hard at all, look at build-unix.txt in the doc/ directory.

Thanks. I tried to compile slimcoind now (using the latest code on git), but compiler (g++ 4.8.2) gets stuck (simply stops to compile) after the following lines:

Code:
main.cpp:994:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   int64 nRewardCoinYear = nTime > POB_POS_TARGET_SWITCH_TIME ? (10 * CENT) : CENT;  // creation amount per coin-year
   ^
main.cpp:1030:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   if(fTestNet || nTime > POB_POS_TARGET_SWITCH_TIME)
   ^
main.cpp:1125:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   if(fTestNet || pindexLast->nTime > POB_POS_TARGET_SWITCH_TIME)
   ^
main.cpp:2380:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
   if(fTestNet || GetBlockTime() > CHAINCHECKS_SWITCH_TIME)

Unfortunately there is no version marked as "stable" which I could try.

Thanks for pointing this out. I will add the folowing change when I next update the client. Try editing main.h. Search for the lines where CHAINCHECKS_SWITCH_TIME and POB_POS_TARGET_SWITCH_TIME are defined. The number they correspond to, add a ULL to the end, no space, ex: 2403654400ULL

Save and recompile.

Tell me if that works.

-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
idad01
Full Member
***
Offline Offline

Activity: 148
Merit: 100


View Profile
July 20, 2014, 08:29:06 AM
 #3431

current number of block 35825?Huh?
ynyjl
Member
**
Offline Offline

Activity: 86
Merit: 10


View Profile
July 20, 2014, 08:39:08 AM
 #3432

current number of block 35825?Huh?

It's short blockchain.
slimcoin (OP)
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile WWW
July 20, 2014, 08:39:54 AM
 #3433

I am currently working on getting the blockchain where it was before.

-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
jadefalke
Legendary
*
Offline Offline

Activity: 1457
Merit: 1014


View Profile
July 20, 2014, 08:57:34 AM
 #3434

appreciate that, looks totaly wired atm.
slimcoin (OP)
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile WWW
July 20, 2014, 10:05:25 AM
 #3435

If you are back at block 35587 or so, there was a fork in the blockchain. The upcoming update will have the hard checkpoints for that fork.
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"

To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155

-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
rfcdejong
Hero Member
*****
Offline Offline

Activity: 798
Merit: 500


View Profile
July 20, 2014, 10:55:09 AM
 #3436

If you are back at block 35587 or so, there was a fork in the blockchain. The upcoming update will have the hard checkpoints for that fork.
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"

To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155

wow, all my 3 wallets on the wrong fork..
primer-
Legendary
*
Offline Offline

Activity: 1092
Merit: 1000



View Profile
July 20, 2014, 11:14:57 AM
 #3437

The fork happened because of the BLOCK PROPAGATION ISSUE i pointed at many many times.

Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.
AizenSou
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


View Profile
July 20, 2014, 11:23:07 AM
 #3438

The fork happened because of the BLOCK PROPAGATION ISSUE i pointed at many many times.

Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.

How many shitcoins did you kill btw, primer- ? You with your CPU farm instamined almost every new coin and dumped it on the market, then you insult everyone who makes you bank ?
 
d5000
Legendary
*
Offline Offline

Activity: 3920
Merit: 6360


Decentralization Maximalist


View Profile
July 20, 2014, 11:24:57 AM
Last edit: July 20, 2014, 12:17:29 PM by d5000
 #3439


Thanks for pointing this out. I will add the folowing change when I next update the client. Try editing main.h. Search for the lines where CHAINCHECKS_SWITCH_TIME and POB_POS_TARGET_SWITCH_TIME are defined. The number they correspond to, add a ULL to the end, no space, ex: 2403654400ULL

Save and recompile.

Tell me if that works.

Had no luck. The warnings are gone when I add ULL to the numbers, but compiler stucks and crashes when compiling main.cpp.

PS: The crash seems to be a RAM issue, so slimcoin has nothing to do with it. Sorry.

PS2: Got it to work now.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
primer-
Legendary
*
Offline Offline

Activity: 1092
Merit: 1000



View Profile
July 20, 2014, 11:25:45 AM
 #3440

The fork happened because of the BLOCK PROPAGATION ISSUE i pointed at many many times.

Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.

How many shitcoins did you kill btw, primer- ? You with your CPU farm instamined almost every new coin and dumped it on the market, then you insult everyone who makes you bank ?
 

I tried to point the dev in the right direction but he is just too stupid. He posted yesterday he was workiing on a FAQ instead of addressing serious issues with the coin. What an idiot.
If you have a block propagation issue it will most definitely lead to a fork. crypto 1-0-1.
Pages: « 1 ... 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 [172] 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!