BANKSYCOIN (SOON TO BE ARTSYCOIN) - ORIGINAL OFFICIAL THREAD

[madmartyk]

I tried to send 100 BSY to Bittrex, never arrived.

[1715376262]

1715376262

[1715376262]

1715376262

[Atomicat]

A fork is usually caused by very low hash rate - whether or not it is more likely when solo mining, I would guess, is dependent on exactly how low that hash rate is. (sort of guessing here) 

I have got to learn more about blockchain construction, what's in it, how to interpret it.  For instance, I just had a quick look through the block explorer in the wallet.  Noticed that there's very erratic hashrates shown there from block to block.  However, when I jump back to say block 200,000 or so I see the same thing.  This scene and it's sparse tool-set has definitely brought out the old coder geek in me but let's just say that the last compiler I used was Borland C++ ... on my 386 (first one was Apple ][ Pascal!)  Not really looking forwards to it but I'm also not looking forwards to being put out on the ice-floe this winter.  S'true, they still do that up here.

[griffitsj]

A fork is usually caused by very low hash rate - whether or not it is more likely when solo mining, I would guess, is dependent on exactly how low that hash rate is. (sort of guessing here) 

I have got to learn more about blockchain construction, what's in it, how to interpret it.  For instance, I just had a quick look through the block explorer in the wallet.  Noticed that there's very erratic hashrates shown there from block to block.  However, when I jump back to say block 200,000 or so I see the same thing.  This scene and it's sparse tool-set has definitely brought out the old coder geek in me but let's just say that the last compiler I used was Borland C++ ... on my 386 (first one was Apple ][ Pascal!)  Not really looking forwards to it but I'm also not looking forwards to being put out on the ice-floe this winter.  S'true, they still do that up here.

The POS (Proof-of-stake) blocks have much lower difficulty than the POW (Proof-of-work) blocks.  That is probably what you are seeing.

[DougB62]

A fork is usually caused by very low hash rate - whether or not it is more likely when solo mining, I would guess, is dependent on exactly how low that hash rate is. (sort of guessing here) 

I have got to learn more about blockchain construction, what's in it, how to interpret it.  For instance, I just had a quick look through the block explorer in the wallet.  Noticed that there's very erratic hashrates shown there from block to block.  However, when I jump back to say block 200,000 or so I see the same thing.  This scene and it's sparse tool-set has definitely brought out the old coder geek in me but let's just say that the last compiler I used was Borland C++ ... on my 386 (first one was Apple ][ Pascal!)  Not really looking forwards to it but I'm also not looking forwards to being put out on the ice-floe this winter.  S'true, they still do that up here.

Guessing by your local time - you in Alaska, or that region, in general?

My first "compiler" (lol!) was this "space age" doo-dad, er.. computer, that I got in 1978 for my 16th birthday. Wow - I feel olllllllldddd! 

[Atomicat]

A fork is usually caused by very low hash rate - whether or not it is more likely when solo mining, I would guess, is dependent on exactly how low that hash rate is. (sort of guessing here) 

I have got to learn more about blockchain construction, what's in it, how to interpret it.  For instance, I just had a quick look through the block explorer in the wallet.  Noticed that there's very erratic hashrates shown there from block to block.  However, when I jump back to say block 200,000 or so I see the same thing.  This scene and it's sparse tool-set has definitely brought out the old coder geek in me but let's just say that the last compiler I used was Borland C++ ... on my 386 (first one was Apple ][ Pascal!)  Not really looking forwards to it but I'm also not looking forwards to being put out on the ice-floe this winter.  S'true, they still do that up here.

Guessing by your local time - you in Alaska, or that region, in general?

My first "compiler" (lol!) was this "space age" doo-dad, er.. computer, that I got in 1978 for my 16th birthday. Wow - I feel olllllllldddd! 

Wow!  You got birthday presents?  Awesome!

Ah, I never bother to set the time-zones on these forums.  I'm from Mantoba where we've had to import our own (look up Red-River floodway).  Great place to do some serous overclocking.

[DeezBTC]

Wus up with the wallet its been out off sync for me for a few days

[roslinpl]

Wus up with the wallet its been out off sync for me for a few days

Bittrex quote: "Blockchain issues..."

I believe it will be soon solved but I haven't got any source of this information

@BanksyCoin devs - what's up with it?

[layer1gfx]

i stopped working for me on wednesday morning as well.
now back to syncing and minting as usual.



exchange issues still unsolved.

[little_kristof]

Wus up with the wallet its been out off sync for me for a few days

Bittrex quote: "Blockchain issues..."

I believe it will be soon solved but I haven't got any source of this information

@BanksyCoin devs - what's up with it?

+1. I hope this problem will be solved quicly.

[madmartyk]

Fired up the wallet, still out of sync and no connections.

[layer1gfx]

even with some nodes in your banksycoin.conf ?

[madmartyk]

Yes
addnode=66.85.133.206:36274
addnode=82.139.116.38:36274

[layer1gfx]

win or linux?

[madmartyk]

win or linux?

Win 7 64 bit. stopped at block 320981

[layer1gfx]

had massive problems to run it under lubuntu 14.04.1 and had to doctor the code until i got it compiled with qt.

let's see if i get stuck as well under win7 32

[banksycoin]

Sorry for the late reply guys, I have been away for a couple of days. There were a few problems with the server but everything should be fixed now. Give it a couple of hours and everything should be working smoothly again.

Thanks for your patience.

[kultus]

patiently awaiting 

[kultus]

patiently awaiting 

Still chilling 

[layer1gfx]

win or linux?

Win 7 64 bit. stopped at block 320981

lubuntu 14.04.1
stopped at 321053 since an hour...

[layer1gfx]

Yes
addnode=66.85.133.206:36274
addnode=82.139.116.38:36274

have this one in the conf as well (and it is the only one that works for me):
addnode=188.226.187.182:36274