[Pushpool Web Frontend] Simplecoin v5.0 Opensource PHP/MySQL - NEW RELEASE - page 5.

simplecoin

sr. member

Activity: 406

Merit: 250

Quote from: sareea on August 10, 2011, 01:18:34 PM

Hello,
When will you release the new updated version ? And will it have sql injection security ?
I really wanna use simplecoin , and if i install the current one is it upgradable to 4 ? I am looking up to open my pool today or tomorrow .
Please answer me

Thanks !

Currently there will not be an easy upgrade path from 2-4. The database changes are drastic.
Version 2 should have sql injection security as should the expirimental branch in the repository.

sareea

member

Activity: 78

Merit: 10

Hello,
When will you release the new updated version ? And will it have sql injection security ?
I really wanna use simplecoin , and if i install the current one is it upgradable to 4 ? I am looking up to open my pool today or tomorrow .
Please answer me

Thanks !

Paul4games

newbie

Activity: 46

Merit: 0

Quote from: simplecoin on August 09, 2011, 07:19:25 PM

Holy incoming updates!

I may have to deem this release 4.0 because the changes are that drastic!

Looking forward for this update.

simplecoin

sr. member

Activity: 406

Merit: 250

Holy incoming updates!

I may have to deem this release 4.0 because the changes are that drastic!

simplecoin

sr. member

Activity: 406

Merit: 250

Quote from: phorensic on August 07, 2011, 11:37:20 AM

Hmm, you must have been using shares_history different that I am. My "shares" is only as large as the current round, old round gets cut and pasted into history. Never have to do joins or unions.

So you throw away the hash data for shares counted? I haven't been brave enough to do that on my history.

I do, once it the round is paid out it's already been verified. I don't see much historical value in past blocks outside of share counts and block finder.

phorensic

hero member

Activity: 630

Merit: 500

Hmm, you must have been using shares_history different that I am. My "shares" is only as large as the current round, old round gets cut and pasted into history. Never have to do joins or unions.

So you throw away the hash data for shares counted? I haven't been brave enough to do that on my history.

simplecoin

sr. member

Activity: 406

Merit: 250

shares is only as large as the current round. Why split that data into 2 tables, when you need to join or union them every time?

after the current round confirms I condense the shares into shares_counted to drastically lower the amount of data.

phorensic

hero member

Activity: 630

Merit: 500

How does your new setup query faster if "sahres" is larger than two tables - "shares" and "shares_history"...besides indexing. Xenland and I have discussed and applied indexing to our setups, so I'm curious.

simplecoin

sr. member

Activity: 406

Merit: 250

Shares history was essentially an extension of shares, but it required lots of additional joins and unions. It made queries painfully processor intensive when they didn't need to be.

Shares counted is the counted sum of valid/invalid shares per round.

As for MyIsam, that was an oversight, I'll fix that before the code is finalized.

phorensic

hero member

Activity: 630

Merit: 500

Quote from: simplecoin on July 22, 2011, 11:32:51 AM

Quote from: AnnihilaT on July 22, 2011, 03:53:48 AM

Quote from: simplecoin on July 21, 2011, 12:38:08 PM

Quote from: mich on July 21, 2011, 11:57:55 AM

Button "Lost Password" is there just for anturage? I haven't found any code serves this event...

It's just a relic from mining pool v1.... Looks like it was a stub. I'll get to it in the next version.

Which reminds me....

v3 features not yet in repo:
Memcached support
No more shares_history (what a nightmare that was)
Improved block handling.
Dynamic stats/setting caching (more responsive/less overhead)
Process locking
Drastically improved cronjobs.
Live round stats.
Just to name a few improvements....

Looking forward to seeing how you have tackled this.... im in the midst of dealing with these same issues... especially the whole shares_history nightmare and the associated monster queries.

Good news then.... I just pushed the initial v3 to the expiremental repo. This is no upgrade script, nor a simple upgrade path... yet. You'll need to merge these as appropriate.

As for moving shares history back into shares (AFTER adding new shares fields), I used this sql:
INSERT INTO shares (username, our_result, time, blockNumber, score) SELECT username, our_result, time, blockNumber, score FROM shares_history WHERE shares_history.counted = '0'

Also, I recommend using a separate instance of memcache than pushpool. Don't want your pool cache eaten by web data.

This is interesting. Can you explain further why you axed shares_history and what shares_counted is for? Is it just a lighter version of shares_history? How big does your original shares table get? I mean, where are your old shares held? I also noticed shares_counted is MyISAM instead of InnoDB, is that because it's a temporary table?

Paul4games

newbie

Activity: 46

Merit: 0

Quote from: simplecoin on August 04, 2011, 02:58:34 PM

Quote from: Paul4games on August 04, 2011, 09:12:34 AM

Siplecoin here is a feature request:
-add an api so that an application could create an new worker when he wants(for example you have 5 computers and you want to create an application that when it's run on that computer it will automatically create an new username+password from that computer+link it to you're account, for example that worker to be linked to my account or so)&retrive them from the server.Or if i'm mining with 2 pcs and using the same username+password is there any problem?or this would work to?

While the idea sounds great, it's also seems like it might add an exploit.

However, you can use the same miner name/pass on multiple workers.

Could you please explain futher what exploit it could add?and i see that you fixed the full path disclousure bugs, good job!

simplecoin

sr. member

Activity: 406

Merit: 250

Quote from: Paul4games on August 04, 2011, 09:12:34 AM

Siplecoin here is a feature request:
-add an api so that an application could create an new worker when he wants(for example you have 5 computers and you want to create an application that when it's run on that computer it will automatically create an new username+password from that computer+link it to you're account, for example that worker to be linked to my account or so)&retrive them from the server.Or if i'm mining with 2 pcs and using the same username+password is there any problem?or this would work to?

While the idea sounds great, it's also seems like it might add an exploit.

However, you can use the same miner name/pass on multiple workers.

Paul4games

newbie

Activity: 46

Merit: 0

Siplecoin here is a feature request:
-add an api so that an application could create an new worker when he wants(for example you have 5 computers and you want to create an application that when it's run on that computer it will automatically create an new username+password from that computer+link it to you're account, for example that worker to be linked to my account or so)&retrive them from the server.Or if i'm mining with 2 pcs and using the same username+password is there any problem?or this would work to?

simplecoin

sr. member

Activity: 406

Merit: 250

Just added capability to offload heavy stats to replicated server (less stress on your pool sql server).

simplecoin

sr. member

Activity: 406

Merit: 250

More updates to v3 pushed to repo.

simplecoin

sr. member

Activity: 406

Merit: 250

Added a forum for discussion and support since I'm often afk in irc. Feel free to give your fellow admins help and share your solutions.

oseido

newbie

Activity: 24

Merit: 0

Hi to all.
We are very impressive about Simplecoin Pushpool Web Frontend. We have start an italian minig pool with this amazing opensource software, and we are in testig. We are also meditating to enable ssl support, but because certificate was self-signed (we have a L.A.M.P system redyrected on dyndns.org) we are finding a way for make certificate not affected about the orrible browser ssl self-signed warning.
We hope tath people can test the server.
Tnx a lot for simplecoin again!!

oseido

Chemtrail Italia Cooperative Bitcoin Mining Pool

http://chemtrail.dyndns.org:8080/
Mining Port = 8332

simplecoin

sr. member

Activity: 406

Merit: 250

Quote from: AnnihilaT on July 22, 2011, 03:53:48 AM

Quote from: simplecoin on July 21, 2011, 12:38:08 PM

Quote from: mich on July 21, 2011, 11:57:55 AM

Button "Lost Password" is there just for anturage? I haven't found any code serves this event...

It's just a relic from mining pool v1.... Looks like it was a stub. I'll get to it in the next version.

Which reminds me....

v3 features not yet in repo:
Memcached support
No more shares_history (what a nightmare that was)
Improved block handling.
Dynamic stats/setting caching (more responsive/less overhead)
Process locking
Drastically improved cronjobs.
Live round stats.
Just to name a few improvements....

Looking forward to seeing how you have tackled this.... im in the midst of dealing with these same issues... especially the whole shares_history nightmare and the associated monster queries.

Good news then.... I just pushed the initial v3 to the expiremental repo. This is no upgrade script, nor a simple upgrade path... yet. You'll need to merge these as appropriate.

As for moving shares history back into shares (AFTER adding new shares fields), I used this sql:
INSERT INTO shares (username, our_result, time, blockNumber, score) SELECT username, our_result, time, blockNumber, score FROM shares_history WHERE shares_history.counted = '0'

Also, I recommend using a separate instance of memcache than pushpool. Don't want your pool cache eaten by web data.

AnnihilaT

full member

Activity: 210

Merit: 100

Quote from: simplecoin on July 21, 2011, 12:38:08 PM

Quote from: mich on July 21, 2011, 11:57:55 AM

Button "Lost Password" is there just for anturage? I haven't found any code serves this event...

It's just a relic from mining pool v1.... Looks like it was a stub. I'll get to it in the next version.

Which reminds me....

v3 features not yet in repo:
Memcached support
No more shares_history (what a nightmare that was)
Improved block handling.
Dynamic stats/setting caching (more responsive/less overhead)
Process locking
Drastically improved cronjobs.
Live round stats.
Just to name a few improvements....

Looking forward to seeing how you have tackled this.... im in the midst of dealing with these same issues... especially the whole shares_history nightmare and the associated monster queries.

simplecoin

sr. member

Activity: 406

Merit: 250

Quote from: mich on July 21, 2011, 11:57:55 AM

Button "Lost Password" is there just for anturage? I haven't found any code serves this event...

It's just a relic from mining pool v1.... Looks like it was a stub. I'll get to it in the next version.

Which reminds me....

v3 features not yet in repo:
Memcached support
No more shares_history (what a nightmare that was)
Improved block handling.
Dynamic stats/setting caching (more responsive/less overhead)
Process locking
Drastically improved cronjobs.
Live round stats.
Just to name a few improvements....

Topic: [Pushpool Web Frontend] Simplecoin v5.0 Opensource PHP/MySQL - NEW RELEASE - page 5. (Read 57208 times)