kslavik
Sr. Member
Offline
Activity: 441
Merit: 250
GET IN - Smart Ticket Protocol - Live in market!
|
|
June 17, 2013, 03:30:49 AM |
|
Here are the potential logos:
I like #3, it will look good in any size, # 1 is not going to look good as a Browser Tab Icon # 2 is ok but round it more common and generic. I would also make #3 look like more like a pie chart from Multiport Section of the website
|
████ ███ ███ ████ ███ ███ ███ ███ ████ ███ ███ ███ ███ ███ ███ ████ ███ ███ ██ ███ ███ █████████████████ ███ ███ ███ ██ ███ ███ ██ ██ ███ ██████████ ███ ███ ██████ ███ ███ ██ ███ ███ ███ ███ ███ ███ ███ ████
| | GUTS | | ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
| | smart-ticket protocol for events ✔ live product with market traction! | | ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
| | ▶ BTC ANN ▶ WEBSITE ▶ BLOG
| | ▶ SANDBOX ▶ WHITEPAPER ▶ BOUNTY
| |
|
|
|
nicksmith
|
|
June 17, 2013, 03:38:35 AM |
|
Looks great, playing around with an android app to display the data. Do you have a logo? I have three, actually. I need to pick one soon and put it on the site. Didn't get as much done as I wanted to this weekend. Also another user requested some API changes which should hopefully make a little more sense.. Check out api2.php. Awesome (I like #1), I threw together a stats pulling app for android https://dl.dropboxusercontent.com/u/42046061/Multipool.apk is the beta test link, I have a market account and can throw it in there when its done. The user data is still json encoded, but it works! Ill tackle the json user data tomorrow.
|
|
|
|
|
gnomicide
|
|
June 17, 2013, 04:00:47 AM |
|
#2 looks the best to me, but I don't like the irregular shape of the central white part.
|
|
|
|
flound1129 (OP)
|
|
June 17, 2013, 04:12:10 AM |
|
I should mention that the logo artwork was donated by user esquinato. I'm not sure if he's active on these boards or not.
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
TheFuneral
|
|
June 17, 2013, 03:51:03 PM |
|
out of curiosity how would being on the multipool that picks the currency help unless you're selling your coins when you mine them? This would also be difficulty with it being PPNS right? What am I missing?
|
|
|
|
ranlo
Legendary
Offline
Activity: 1988
Merit: 1007
|
|
June 17, 2013, 03:52:39 PM |
|
out of curiosity how would being on the multipool that picks the currency help unless you're selling your coins when you mine them? This would also be difficulty with it being PPNS right? What am I missing?
You're essentially right. I'm mostly on it because it jumps around and so I'm mining many different coins over time; think of it as spreading yourself out over investments.
|
|
|
|
flound1129 (OP)
|
|
June 17, 2013, 03:57:16 PM Last edit: June 17, 2013, 04:21:48 PM by flound1129 |
|
out of curiosity how would being on the multipool that picks the currency help unless you're selling your coins when you mine them? This would also be difficulty with it being PPNS right? What am I missing?
Coin profitability fluctuations are mostly due to difficulty changes. Price fluctuation plays a small part. Unless a coin crashes in value you should be able to sell it for close to what it was when we were mining it. Most of our coins pay out after 20 confirms or less. I'm planning to implement an "actual profitability" for last 24h but there are some challenges involved.
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
nicksmith
|
|
June 17, 2013, 05:34:41 PM |
|
ooh thats nicer, are you going to move that to api.php or should i point to api3.php?
|
|
|
|
flound1129 (OP)
|
|
June 17, 2013, 05:50:14 PM |
|
ooh thats nicer, are you going to move that to api.php or should i point to api3.php? I was going to move it to api.php as long as everyone was OK with that.
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
kslavik
Sr. Member
Offline
Activity: 441
Merit: 250
GET IN - Smart Ticket Protocol - Live in market!
|
|
June 17, 2013, 06:00:12 PM |
|
ooh thats nicer, are you going to move that to api.php or should i point to api3.php? I was going to move it to api.php as long as everyone was OK with that. I'm ok with that. There is still Pool Hashrates section, which is redundant with the same data under currencies. Alternately it (pool hash rates and other pool related data) could be separated to an alternative API call for Pool Data only, so it could be accessed by other services without a need to create a user inside the system. I don't think Alive is needed inside Workers table - if hash rate is 0, the worker is not alive.
|
████ ███ ███ ████ ███ ███ ███ ███ ████ ███ ███ ███ ███ ███ ███ ████ ███ ███ ██ ███ ███ █████████████████ ███ ███ ███ ██ ███ ███ ██ ██ ███ ██████████ ███ ███ ██████ ███ ███ ██ ███ ███ ███ ███ ███ ███ ███ ████
| | GUTS | | ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
| | smart-ticket protocol for events ✔ live product with market traction! | | ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
| | ▶ BTC ANN ▶ WEBSITE ▶ BLOG
| | ▶ SANDBOX ▶ WHITEPAPER ▶ BOUNTY
| |
|
|
|
kslavik
Sr. Member
Offline
Activity: 441
Merit: 250
GET IN - Smart Ticket Protocol - Live in market!
|
|
June 17, 2013, 06:09:38 PM Last edit: June 17, 2013, 09:10:48 PM by kslavik |
|
I noticed a small bug:
Inside Pool Stats->MNC:
Sum of "TOP 10 HASHERS" valid shares is 2x of the "Current N (Round Shares)" (on the same page) (probably due to different difficulties used)
Please increase "Current N Shares" or decrease "Valid Shares". The sum of the Current Round Valid Shares should be equal to Current N (Round Shares).
Thank you
|
████ ███ ███ ████ ███ ███ ███ ███ ████ ███ ███ ███ ███ ███ ███ ████ ███ ███ ██ ███ ███ █████████████████ ███ ███ ███ ██ ███ ███ ██ ██ ███ ██████████ ███ ███ ██████ ███ ███ ██ ███ ███ ███ ███ ███ ███ ███ ████
| | GUTS | | ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
| | smart-ticket protocol for events ✔ live product with market traction! | | ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███ ███
| | ▶ BTC ANN ▶ WEBSITE ▶ BLOG
| | ▶ SANDBOX ▶ WHITEPAPER ▶ BOUNTY
| |
|
|
|
flound1129 (OP)
|
|
June 17, 2013, 06:52:24 PM |
|
ooh thats nicer, are you going to move that to api.php or should i point to api3.php? I was going to move it to api.php as long as everyone was OK with that. I'm ok with that. There is still Pool Hashrates section, which is redundant with the same data under currencies. Alternately it (pool hash rates and other pool related data) could be separated to an alternative API call for Pool Data only, so it could be accessed by other services without a need to create a user inside the system. I don't think Alive is needed inside Workers table - if hash rate is 0, the worker is not alive. The api returns pool data only, if there is no api key in the URL. Specific coin data can also be returned by using https://multipool.in/api.php?curr=ltc (for example)
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
|
flound1129 (OP)
|
|
June 17, 2013, 07:05:00 PM |
|
OK, api3 is still there. I copied it to api.php.
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
nicksmith
|
|
June 17, 2013, 07:19:51 PM |
|
OK, api3 is still there. I copied it to api.php. tiny favor? can you put " around all zero's? You have it on everything else that is a zero value except estimated_rewards and it throws up errors since its not consistant
|
|
|
|
jaywaka2713
Sr. Member
Offline
Activity: 266
Merit: 250
aka 7Strykes
|
|
June 17, 2013, 07:28:38 PM |
|
Would you consider implementing the BTC-E API into your site? That would allow us to directly or automatically sell our altcoins at the market value, or set our own prices and sell them at those prices as they are generated. Could be done if you implement a limit of 1 coin of whatever currency before your sell order goes live, and sell order can only be increased by 1 coin intervals.
|
|
|
|
flound1129 (OP)
|
|
June 17, 2013, 08:32:06 PM |
|
Would you consider implementing the BTC-E API into your site? That would allow us to directly or automatically sell our altcoins at the market value, or set our own prices and sell them at those prices as they are generated. Could be done if you implement a limit of 1 coin of whatever currency before your sell order goes live, and sell order can only be increased by 1 coin intervals.
That'd be a rather large project that I don't have time for at the moment.. If someone is willing to implement it in PHP I would consider adding it.
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
TheFuneral
|
|
June 17, 2013, 08:40:16 PM Last edit: June 17, 2013, 09:23:39 PM by TheFuneral |
|
out of curiosity how would being on the multipool that picks the currency help unless you're selling your coins when you mine them? This would also be difficulty with it being PPNS right? What am I missing?
Coin profitability fluctuations are mostly due to difficulty changes. Price fluctuation plays a small part. Unless a coin crashes in value you should be able to sell it for close to what it was when we were mining it. Most of our coins pay out after 20 confirms or less. I'm planning to implement an "actual profitability" for last 24h but there are some challenges involved. Ahh I supposed that makes sense in theory. I haven't done any practical testing to verify it, but thanks for your input! I'll look for the actual profit in the future. What are the challenges you're hitting? Why does coinchoose and coinwarz disagree with your predictions of profit?
|
|
|
|
gnomicide
|
|
June 17, 2013, 09:53:38 PM |
|
Would you consider implementing the BTC-E API into your site? That would allow us to directly or automatically sell our altcoins at the market value, or set our own prices and sell them at those prices as they are generated. Could be done if you implement a limit of 1 coin of whatever currency before your sell order goes live, and sell order can only be increased by 1 coin intervals.
That'd be a rather large project that I don't have time for at the moment.. If someone is willing to implement it in PHP I would consider adding it. I'm about 75% done the back-end of a stand-alone auto-sell service. In Ruby. The only obstacle I'm facing is transaction fees. Transfer 1 brand-new LTC and it takes a 10% fee! I'd probably just set a 10 coin threshold, otherwise it'd take a ton of confirms to eliminate the transfer fee. I hope at the pool, the transaction fees for those taking low-threshold payouts is applied to them alone and not shared across the pool... The fact the exchanges don't (from what I can see) offer a withdraw API (for the sold BTC) adds a bit extra risk to the equation too. I'd be giving out my local BTC, and manually refilling from the account. Maybe the simplest would be to just let have users enter their API and private keys (of a new account only used for this), and they send their mining payouts directly to the exchange, and the service just executes the auto-sells. They can then withdraw their BTC at their leisure.
|
|
|
|
|