Pages:
Author

Topic: Slimcoin | First Proof of Burn currency | Decentralized Web - page 95. (Read 137076 times)

aIA
newbie
Activity: 31
Merit: 0
Anybody are suffering the same symptoms?

Yes. eliteyo is.

I wonder if it's possibly due to platform+OS differences in C++ implementation:

https://github.com/slimcoin-project/Slimcoin/commit/8e9fe2c832e62ba60dc57aacef52918ba2d115fb#diff-7ec3c68a81efff79b6ca22ac1f1eabbaL5306

I doubt I can replicate on a VM. If anyone's experiencing that problem and is compiling natively for Windows, does reverting that line to the C99 macro fix it?

Cheers

Graham

The Slimcoin version 0.5.0 is not working properly on any of my ARM boards (Raspberry Pi & Odroid XU4) even if I manage to compile it properly. It crashes randomly and my debugging skills got me as far as dumping a core and investigating the stack frames, but no useful thing came out of this.

My hunch is that it may have something to do with the boost libraries. But I may be wrong.

In have just found this doc on github about compiling bitcoin for differents platforms.


https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md

Take a look at the section "ARM Cross-compilation".

Could anybody try it? Maybe I could try this weekend.

member
Activity: 92
Merit: 10
Funny thing happened. I have a dedicated Slim Burn wallet on a computer I use only for this wallet (i.e. my staking Slim wallet does not reside on this computer).  Anyway, regular and healthy sized payouts of coins had been coming in thanks to burning.

After a couple weeks the staking started up (I suppose because my wallet was unlocked).  Staking rewards suddenly started appearing.

Exactly coinciding with the onset of staking rewards, 1) my computer slowed way down and 2) the burn payouts reduced to a trickle and became smaller in size. Though I was now getting small stake returns, this didn't compensate for the huge reduction in burn payouts.  

I'm assuming I shouldn't have left the wallet unlocked on my dedicated "burning wallet/computer" because staking takes too much processor power, even for small amounts.

What I learned is not to mix burning and staking, and therefore, to always burn with the wallet locked.  

The thing I can't explain is why the onset of staking rewards would reduce burn rewards.  Although the computer was slow, it was working enough to support several other non-Slimcoin wallets that continued to get staking rewards, and I understand burning isn't processor intensive.  So I'm a bit perplexed why my burn rewards got reduced by 90%.  
legendary
Activity: 1806
Merit: 1001
How often do you get PoS rewards? I staked last week and got some coins on the first day (like 47 coins with a stake of 19600) but haven't got anything in a week. Does the amount sound right as well?

You get to receive 10% of your stake yearly which is 1960 coins. It's 5.36 coins a day.
member
Activity: 81
Merit: 10
How often do you get PoS rewards? I staked last week and got some coins on the first day (like 47 coins with a stake of 19600) but haven't got anything in a week. Does the amount sound right as well?
full member
Activity: 196
Merit: 135
Sit back, relax, eat some nachos and have a drink.
I'm looking over the block creation code (https://github.com/slimcoin/slimcoin/blob/afd8ef7e18e17f876f0bc7b44e79ee867f0b3ac1/src/main.cpp#L4931) and I'm wondering:

What is stopping miners from changing the block decay to a constant? What is stopping them from replacing that whole statement with something that makes nEffectiveBurnCoins an absurdly high number?

Someone can burn coins have them never decay D:
full member
Activity: 196
Merit: 135
Sit back, relax, eat some nachos and have a drink.
The Slimcoin version 0.5.0 is not working properly on any of my ARM boards (Raspberry Pi & Odroid XU4) even if I manage to compile it properly. It crashes randomly and my debugging skills got me as far as dumping a core and investigating the stack frames, but no useful thing came out of this.

My hunch is that it may have something to do with the boost libraries. But I may be wrong.

Run it through strace and gdb.
member
Activity: 98
Merit: 10
The Slimcoin version 0.5.0 is not working properly on any of my ARM boards (Raspberry Pi & Odroid XU4) even if I manage to compile it properly. It crashes randomly and my debugging skills got me as far as dumping a core and investigating the stack frames, but no useful thing came out of this.

My hunch is that it may have something to do with the boost libraries. But I may be wrong.
legendary
Activity: 2254
Merit: 1290
Anybody are suffering the same symptoms?

Yes. eliteyo is.

I wonder if it's possibly due to platform+OS differences in C++ implementation:

https://github.com/slimcoin-project/Slimcoin/commit/8e9fe2c832e62ba60dc57aacef52918ba2d115fb#diff-7ec3c68a81efff79b6ca22ac1f1eabbaL5306

I doubt I can replicate on a VM. If anyone's experiencing that problem and is compiling natively for Windows, does reverting that line to the C99 macro fix it?

Cheers

Graham
hero member
Activity: 819
Merit: 502

Try with this:

sudo apt-get install git build-essential libssl-dev libdb5.3++-dev libminiupnpc-dev libboost-all-dev qt5-qmake libqt5gui5 qt5-default qtdeclarative5-dev qttools5-dev-tools libqt5dbus5
git clone https://github.com/slimcoin-project/Slimcoin/
cd Slimcoin
git checkout master
cd src
make -f makefile.unix

Thank you so much!! It seems work perfectly!!!



You are welcome!!! Enjoy in SLM


Hi, today I have been done more intensive testing of Raspi Slimcoin daemon and it crash every time it try to do PoB, I think. My wallet it's encrypted, I have burnt some coins on windows client before copy Blockchain and wallet files to Raspberry. Trying to mint by burn with Pi, I unlock wallet with "./slimcoind walletpassphrase pass 100000 true" and immediately it crash.... there's last lines of debug.log:

Code:
trying connection 39.50.208.44:41682 lastseen=-15495.2hrs
connection timeout
trying connection 173.102.114.151:41682 lastseen=-26962.5hrs
ThreadRPCServer method=walletpassphrase
connection timeout
SlimCoinAfterBurner():
        Smallest Hash is 0000003138af0000000000000000000000000000000000000000000000000001
        by tx 1f1b6e070f59560cb86d919d2f37faeac9faafb5f51762cc46b16e5b11d45c89
        with Block height 976294, transaction depth 2, vout depth 1
        PoB Tartget is 0000000088be0000000000000000000000000000000000000000000000000000
pi@PiServer:~/hdd1/Slimcoin $

Anybody are suffering the same symptoms?

If you have problem with 0.5 try 0.4 wallet, it was working very well as well
aIA
newbie
Activity: 31
Merit: 0
I dont understand something:

Explorers on slimcoin.info and Bchain.info showing different things for the same blocks?

I think all it´s correct... explorer on Slimcoin.club sometime not showing you the block you select... example: you select 1076472 and it show you "height": 1076476". Make sure it´s showing the block you desire.
aIA
newbie
Activity: 31
Merit: 0

Try with this:

sudo apt-get install git build-essential libssl-dev libdb5.3++-dev libminiupnpc-dev libboost-all-dev qt5-qmake libqt5gui5 qt5-default qtdeclarative5-dev qttools5-dev-tools libqt5dbus5
git clone https://github.com/slimcoin-project/Slimcoin/
cd Slimcoin
git checkout master
cd src
make -f makefile.unix

Thank you so much!! It seems work perfectly!!!



You are welcome!!! Enjoy in SLM


Hi, today I have been done more intensive testing of Raspi Slimcoin daemon and it crash every time it try to do PoB, I think. My wallet it's encrypted, I have burnt some coins on windows client before copy Blockchain and wallet files to Raspberry. Trying to mint by burn with Pi, I unlock wallet with "./slimcoind walletpassphrase pass 100000 true" and immediately it crash.... there's last lines of debug.log:

Code:
trying connection 39.50.208.44:41682 lastseen=-15495.2hrs
connection timeout
trying connection 173.102.114.151:41682 lastseen=-26962.5hrs
ThreadRPCServer method=walletpassphrase
connection timeout
SlimCoinAfterBurner():
        Smallest Hash is 0000003138af0000000000000000000000000000000000000000000000000001
        by tx 1f1b6e070f59560cb86d919d2f37faeac9faafb5f51762cc46b16e5b11d45c89
        with Block height 976294, transaction depth 2, vout depth 1
        PoB Tartget is 0000000088be0000000000000000000000000000000000000000000000000000
pi@PiServer:~/hdd1/Slimcoin $

Anybody are suffering the same symptoms?
hero member
Activity: 819
Merit: 502
I have contacted B-ter to reconsider again SLM. They answered like "Thanks for the information"
hero member
Activity: 819
Merit: 502
I dont understand something:

Explorers on slimcoin.info and Bchain.info showing different things for the same blocks?
aIA
newbie
Activity: 31
Merit: 0
 Grin Now my Pi is a farming Storj node and SLM burning machine  Grin
legendary
Activity: 2254
Merit: 1290
It seems work perfectly!!!

Good to know because ...



Hmm.

Cheers

Graham
hero member
Activity: 819
Merit: 502

Try with this:

sudo apt-get install git build-essential libssl-dev libdb5.3++-dev libminiupnpc-dev libboost-all-dev qt5-qmake libqt5gui5 qt5-default qtdeclarative5-dev qttools5-dev-tools libqt5dbus5
git clone https://github.com/slimcoin-project/Slimcoin/
cd Slimcoin
git checkout master
cd src
make -f makefile.unix

Thank you so much!! It seems work perfectly!!!



You are welcome!!! Enjoy in SLM
aIA
newbie
Activity: 31
Merit: 0

Try with this:

sudo apt-get install git build-essential libssl-dev libdb5.3++-dev libminiupnpc-dev libboost-all-dev qt5-qmake libqt5gui5 qt5-default qtdeclarative5-dev qttools5-dev-tools libqt5dbus5
git clone https://github.com/slimcoin-project/Slimcoin/
cd Slimcoin
git checkout master
cd src
make -f makefile.unix

Thank you so much!! It seems work perfectly!!!

hero member
Activity: 819
Merit: 502
aIA
newbie
Activity: 31
Merit: 0
Hi guys, I have been playing some time trying to compile Slimcoin daemon on Raspberry Pi (slimcoind on Raspbian headless server), and that´s my results:

v0.4.0 Compile and run smoothly but it has a warning ( "WARNING: Blockchain re-download required approaching or past V0.4 upgrade deadline") that make it run on safe mode and I can´t do almost any thing on command line console, I allways get that warning; still it updates well the blocks and stay online.

The sync allways stop on block 350. To work around that, I copied blockchain files from my Windows wallet.

v0.5.0 Compilation was allrigth, but it crashes all the time (every 3 o 5 mins). Can´t sync. Always stop on block 500. I get connecction refused, socket closed mensajes on debug.log. Need to add USE_OLDC=1 to get compiled, otherwise it is hung in the file bitcoinrpc.cpp.

That´s the step I have done (I'm not Linux expert so if you can help me I'll be very greatful):

Code:

sudo apt-get update

sudo apt-get upgrade

sudo apt-get install build-essential libssl-dev libboost-all-dev libminiupnpc-dev

mkdir Slimcoin && cd Slimcoin

wget https://github.com/slimcoin-project/Slimcoin/archive/SLMv0.5.0.tar.gz && tar xvfz SLMv0.5.0.tar.gz

wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz && tar xvfz db-4.8.30.NC.tar.gz

cd db-4.8.30.NC/build_unix

../dist/configure --enable-cxx --disable-shared --with-pic CPPFLAGS="-I/usr/local/BerkeleyDB.4.8/include -O2" LDFLAGS="-L/usr/local/BerkeleyDB.4.8/lib"

make && sudo make install

cd /home/pi/Slimcoin/Slimcoin-SLMv0.5.0/src

make -f makefile.unix USE_OLDC=1 BDB_INCLUDE_PATH='/usr/local/BerkeleyDB.4.8/include' BDB_LIB_PATH='/usr/local/BerkeleyDB.4.8/lib'

sudo ln -s /usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.so /usr/lib/libdb_cxx-4.8.so


Just run daemon:

./slimcoind


(Get warning mensaje about slimcoin.conf and closed but it has created wallet files)


Now I will change the wallet files from sd to external hard drive.



mv /home/pi/.slimcoin /home/pi/hdd1

mkdir /home/pi/.slimcoin && cd /home/pi/.slimcoin

sudo nano slimcoin.conf

Create slimcoin.conf in .slimcoin folder on sd.

addnode=113.106.95.46:41682
addnode=118.126.8.18:41682
addnode=130.255.73.170:41682
addnode=144.76.64.49:41682
addnode=149.169.122.151:41682
addnode=149.169.123.98:41682
addnode=161.53.40.94:41682
addnode=175.195.8.141:41682
addnode=185.68.67.37:41682
addnode=37.187.100.75:41682
addnode=37.191.207.237:41682
addnode=192.168.1.5:41682
addnode=5.9.39.9:41682
addnode=59.12.96.208:41682
addnode=82.201.217.74:41682


datadir=/home/pi/hdd1/.slimcoin
reservebalance=1000000
daemon=1
MAX_ORPHAN_BLOCKS=200
rpcuser=user
rpcpassword=pass
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcport=41683
port=41682
server=1
listen=1

- - - - -


Move executable slimcoind to hdd and create cron job


mkdir /home/pi/hdd1/Slimcoin

cp /home/pi/Slimcoin/Slimcoin-SLMv0.5.0/src/slimcoind /home/pi/hdd1/Slimcoin

sudo rm -r /home/pi/Slimcoin

cd /home/pi/hdd1/Slimcoin

./slimcoind



crontab -e

@reboot sleep 60 && /home/pi/hdd1/Slimcoin/slimcoind


Added: At the moment, can´t use any of this versions on Pi. Perhaps the v0.4.0 modified to remove the warning could be useful.
sr. member
Activity: 882
Merit: 310
My assumption is plain simple - I wouldn't expect any reward (as me, if I have eg 500K SLM), let alone so much that was boggling network (and still is) for a few days with only POS blocks, when I wouldn't within network as a node for 1-2-3-xx years.
I'm not 'agressive' or 'angry'. Just sad that, the code doesn't mind if you stake day-by-day or you just run it once in a few years.
If I can I would just buy all the supply of SLMs now (yeah I could with some difficulties, but in the end I would do it, if it was only market cap), and just stake every few years. Then network would be boggled not for a few days but for a weeks, but I would be 'HODLER' that believed in project.
I don't what to say more.
It's everything I can say to support my case.

I have quite big plans with this project, to develop it further, in various ways, but we must agree to some degree, with some things/cases.
Pages:
Jump to: