Topic: [ANN][PASL]-[PASCAL Lite]-[The Future is Almost Here] - page 47. (Read 164913 times)

For accounts you have to do so:

-dpool stratum+tcp://pasl.fairpool.xyz:4009 -dwal PUBKEY.hereyourpublickey -dpsw x -dcoin pasc -allpools 1

Dashboard: PUBKEY.hereyourpublickey

I started mining on the pasl.fairpool.xyz pool.
My settings look like this.

-dpool stratum+tcp://pasl.fairpool.xyz:4009 -dwal 138679-36 -dpsw x -dcoin pasc -allpools 1

Coins come to me. But do not come accounts.
Or maybe I'm not looking properly?
On the pool it is written that with every 12.5 pascal accounts will come, but they are not.
http://i68.tinypic.com/24b2mir.png
http://i68.tinypic.com/2m5fokj.png

PascalLite AT THE MOMENT IS NOT LISTED ON POLONIEX

Seems people are sending money into PascalLite account #86646-64 which is the Poloniex PascalCoin deposit address. If you send the coins into account #86646-64 you are basically sending to an unknown individual who might not send them back.

There is a bug with the Claymore miner and it processes work too slow, that's why you get a huge rejection rate.

You need to contact him and see if he can fix the bug. We tried but got no response.

If you don't want these rejects then use SGMINER, however you can't dual with that miner.

rejection % is average to 6% of shares is it normal?

I prefer to solo mining but cant connect using claymore miner 

Small number of rejects is normal depending which miner you are using.

Hashrate is always generally incorrect on most pools.

is there any other pool than suprnova and fairpool?

i keep disconnected from suprnova, and my share got many rejected, also the hashrate reading is wrong.

Yes looking at the block times its fairly consistent now and should yield ~288 blocks per day. And the difficulty also seems to stay somewhat constant throughout the day and should provide more accurate "WhattoMine" calculations.




For everybody claiming that this was a simple fix, you need to understand that its a simple fix BEFORE a coin actually is launched. After its launched you need to add certain coding to perform a careful hard-fork which won't disrupt the network. This is no different then what is going on with the Bitcoin scaling debate. It only takes 1 line to change but since the network is already launched, it takes more lines of code to perform it safety. That's why its a controversial  matter.

yobit is HORRIBLE

... I don´t believe the code changes in PASL have been done in 10 minutes nor 1 hour so far - if you need 10 minutes to compile, you should get yourself a new PC ^^ .

I don´t understand what´s the fuzz about yobit and btc38.

(respectfully)

Yeah, it took 31 sec 157 ms for us.

People will start throwing hash on rent after they realize it's profitable. I didn't expect to see another pascal around but glad I see it and can physically touch it. Little improvements like these posted above will be reflective in coin valuation when the community proves there's a demand for another pascal coin. Nonetheless it looks like a tremendous achievement.

Average blocktime seems to be way much better than it was before! But we haven't seen any big nicehash rents yet.

Anyways great job xiphon!!!

These are minor changes that literally take an hour. I could tune it up within 10 minutes and could even build the GUI if I had another 10 minutes. Overall its nice that the progress is being made and this fact alone deserves noting. Im not into expanse anymore and will be looking to acquire pasc lite after it goes past yobit and lands on btc38.

Hi Folks,

according to what I can see, PASL runs much smoother now,
this project is getting better and better.

THX to the DEVs (no more copycats) !


 

Added: Socks5 support - Now you can use PascalLite through TOR network
Changed: difficulty
Changed: UI minor changes
Refactoring: useless code dropped
Refactoring: warnings
Fixed: networking, connections statistic


- The hardfork was implemented to change the difficulty settings.  The difficulty was refactoring based on the past 100 blocks. Now it refactors based on the past 10. This is to prevent some of the exploiting that has been being done by renting hash when the difficulty is going down. The hashrate would increase by .5 to 1 gigahash on the network.... but the difficulty would keep going down.  The person renting the hash would hit a bunch of quick blocks.  But the network would take a long time to react to that.  The person could start hitting really quick blocks and the network would keep lowering the difficulty because it was looking at the past 100 blocks.

When the network would recover the difficulty would go up way too high. The person(s) renting hash would stop renting hash. Then the network might take 8-12 hours to recover.  During that time instead of blocks being found every 5 minutes they might be found 2-3 times an hour.  It was screwing up the network for everyone.

Now the system reacts much faster so if someone rents a lot of hash they can't exploit the network as much... and it doesn't hurt the rest of the miners that aren't trying to exploit it.

Win win solution. Well done devs.

BITTREX?

Its not possible with the protocol unfortunately. You would need to use SGMINER

hi is there any tutorial to solo mining pascal lite using claymore dual miner?

Project (menu)-> Private keys (item) -> Export public key (button).