[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 30.

sleepdog

full member

Activity: 183

Merit: 100

Quote from: 95A31 on August 20, 2014, 05:54:27 AM

It will provide only a webpage of pool status like this:

other information can be retrieved by exploring the blockchain.

I'm interested to see exactly what you're going to do with these coins....

Quote

pay

/peɪ/

verb
Nautical

past tense: payed; past participle: payed

seal (the deck or seams of a wooden ship) with pitch or tar to prevent leakage.

"an open groove between the planks had to be payed by running in hot pitch from a special ladle"

slimcoin

full member

Activity: 182

Merit: 100

There will always be an intrinsic danger for using any type of pool. The safest way to use PoB pools is to send small amounts, amounts that if lost, will not be significant. Once a portion have been decayed, you send more again and keep a steady rate of active burnt coins at a time instead of one big chunk in the beginning.

m5j0r

full member

Activity: 140

Merit: 100

Not gonna get my coins then.
This should come from the devs - they don't seem to be very competent looking at the loss of coins etc but they still would be the only random entity I'd trust bought/mined SLMs with.

95A31

newbie

Activity: 12

Merit: 0

Quote from: m5j0r on August 20, 2014, 12:35:34 AM

Quote from: primer- on August 19, 2014, 12:40:53 PM

Quote from: 95A31 on August 19, 2014, 12:39:08 PM

An alpha version of my PoB Pool coming soon. Looking for testers.

Cant wait to see how many dumb suckers send coins your way

Is there a way to join the PoB pool without trusting coins to some random internet stranger? Like a trustless solution?

If there is, I not found it.

I want to be clear and honest from now.

I will not release the source code of pool because it is write from scratch by me and I do not want clones of my work. If someone is curious and want see parts of code, he can contact me by PM.
The pool's fee will be 2%:
- 1% regular fee
- 1% will be burned
It will provide only a webpage of pool status like this:
http://i62.tinypic.com/2ni1lif.png
other information can be retrieved by exploring the blockchain.

hankrules

hero member

Activity: 673

Merit: 500

Is the network stable? I rented a bunch of amazon rivers at the start. I generate quite a few slims each day and would like to see this project succeed.

m5j0r

full member

Activity: 140

Merit: 100

Quote from: primer- on August 19, 2014, 12:40:53 PM

Quote from: 95A31 on August 19, 2014, 12:39:08 PM

An alpha version of my PoB Pool coming soon. Looking for testers.

Cant wait to see how many dumb suckers send coins your way

Is there a way to join the PoB pool without trusting coins to some random internet stranger? Like a trustless solution?

rfcdejong

hero member

Activity: 798

Merit: 500

Quote from: slimcoin on August 18, 2014, 01:37:12 PM

Whoever has such exceptions and can compile their client from source, please do so. I have made changes to fix the wallet of such exceptions, it is the latest commit on github. I have never experienced such issues and cannot test if the additions will fix anything. I have tested them to prove they work but am not sure if the exceptions will no longer occur.

I turned off listen=1 in my .conf file and the exception is gone, without a new build

hankrules

hero member

Activity: 673

Merit: 500

Quote from: 95A31 on August 19, 2014, 12:39:08 PM

An alpha version of my PoB Pool coming soon. Looking for testers.

I'll help test. Need some connection info.

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: 95A31 on August 19, 2014, 12:39:08 PM

An alpha version of my PoB Pool coming soon. Looking for testers.

Cant wait to see how many dumb suckers send coins your way

95A31

newbie

Activity: 12

Merit: 0

An alpha version of my PoB Pool coming soon. Looking for testers.

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: slimcoin on August 18, 2014, 01:37:12 PM

Whoever has such exceptions and can compile their client from source, please do so. I have made changes to fix the wallet of such exceptions, it is the latest commit on github. I have never experienced such issues and cannot test if the additions will fix anything. I have tested them to prove they work but am not sure if the exceptions will no longer occur.

Fairly certain that the new commits will fix what is essentially a RAM issue.

~ I've seen the EXCEPTION: St9bad_alloc over flows on a system with comparatively low RAM, although a system with 16 GB of RAM appears mostly stable.

Has anyone else seen a Microsoft Visual C++ Runtime Library APPCRASH seemingly unrelated to the exception ? Which seems to happen more frequently when solo mining and/or PoS minting using an unlocked wallet ?

slimcoin

full member

Activity: 182

Merit: 100

Whoever has such exceptions and can compile their client from source, please do so. I have made changes to fix the wallet of such exceptions, it is the latest commit on github. I have never experienced such issues and cannot test if the additions will fix anything. I have tested them to prove they work but am not sure if the exceptions will no longer occur.

rfcdejong

hero member

Activity: 798

Merit: 500

Quote from: rfcdejong on August 17, 2014, 04:23:15 PM

Quote from: slimcoin on August 17, 2014, 02:41:35 PM

As for the bad alloc exception, I looked around and found an explanation that is probably the solution:

From https://github.com/bitcoin/bitcoin/issues/2353

Quote

This is how bitcoin runs out of memory (virtual address space) while downloading blocks:

Whenever a node receives a block that it cannot link to the chain, it stores it in memory in mapOrphanBlocks. There is no limit to the size of that data. When a node is downloading blocks, it may download and keep in memory many blocks that it can't currently link to the chain. In particular, if your node connects to another node which is also downloading blocks and which is further along in the download, the other node will spam your node with an "inv" message for every new block that it downloads (no, the logic in CBlock::AcceptBlock does not prevent it), and your node will download and store those blocks in mapOrphanBlocks. This can occur with multiple connected nodes simultaneously which are at different points in the download.

I encountered this problem several times with 0.8.0rc1. With the current size of the blockchain, it is not hard to exhaust the virtual address space (at most 4GiB) in 32-bit builds, which includes all Windows builds.

The fix could proceed in one of two directions: (1) store orphan blocks on disk instead of in memory, or (2) don't keep an unbounded set of orphan blocks. For (2), the ideal would be to prevent downloading of too many orphans rather than discarding orphans that have already been downloaded, which is wasteful. The goal would be to download blocks roughly in order. One idea is to make use of "getheaders" during block download. Headers would be downloaded and linked together, and blocks would only be downloaded if we already know based on headers that they are not too far away from the chain of blocks that we already have.

How much memory does your system have?

I could implement the second option, but will look into how bitcoin fixed this issue.

Also, if you have any other exceptions, please post them.

the exception is still being thrown, my system has 1.9 GB in use out of 8 GB.. 64 bit

i just deleted my blockchain and took a backup from 8 august, it's syncing again and i will see if this will still happen or not. Perhaps it was just because i had too many orphans indeed..

My wallet crashed again with a fresh blockchain.. same exception
Maybe it's because too many nodes connect to me since i configured my router to route inbound over the slimcoin port to my wallet?

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: SpeedDemon13 on August 18, 2014, 02:57:20 AM

So, those are the official addnodes we use from now on or is there any other we have to use?

If your able to reach IP 76.127.202.17 then you should first fully sync the blockchain using the following in slimcoin.conf ;

listen=0
maxconnections=1
connect=76.127.202.17

When you are fully synced you should shutdown slimcoin and alter the config. ;

listen=1
maxconnections=8 (or more)
addnode=76.127.202.17
addnode=107.181.250.216
addnode=107.181.250.217

Which should help you to bootstrap more p2p connections to updated nodes.

My nodes are not 'official' slimcoin nodes, although these vps servers have good uptime and I will try to ensure that they stay up and running.

SpeedDemon13

hero member

Activity: 518

Merit: 500

Quote from: slimcoin on August 17, 2014, 10:58:37 PM

BitcoinFX was kind enough to offer his nodes, once your are done syncing from the main seed node, you could add his nodes also.

addnode=107.181.250.216
addnode=107.181.250.217

So, those are the official addnodes we use from now on or is there any other we have to use?

slimcoin

full member

Activity: 182

Merit: 100

True, but it is explicitly stated in COPYING.
Regardless, the point is understood.

Currently I am working on getting more publicity for Slimcoin. Many exchanges use a voting system to get a currency onto it.
The question is, is voting the best way? Another option would be to write to the exchange personally to attract their attention.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: slimcoin on August 18, 2014, 02:17:31 AM

I restated that license to clarify that I will not be reimbursing any losses as people were complaining about burning too many coins and not seeing an immediate return, etc.

Understood, but you don't even seem to be quoting the correct licence.

slimcoin

full member

Activity: 182

Merit: 100

I restated that license to clarify that I will not be reimbursing any losses as people were complaining about burning too many coins and not seeing an immediate return, etc.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: slimcoin on August 17, 2014, 02:29:14 PM

I would like to remind all of you that Slimcoin is released under the GPL licence found at: https://www.gnu.org/copyleft/gpl.html

As quoted in Section 15:

Quote

EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO ...

Where in the source tree does it say it is GPL'd? The file COPYING in the root seems to imply that you can do what you like, so long as you retain the original copyright notice.

Also, why are you asserting the licence? I'm curious why this message seems to have been written out of the blue.

slimcoin

full member

Activity: 182

Merit: 100

BTER is back on the correct fork.

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 30. (Read 284948 times)