Search content
Sort by
Showing 17 of 17 results by BenFranklin
Thanks, working on it. http://explorer.spotmecoin.com/ works fine
Big news! Our blockchain explorer is now available. Get a peak at it before we announce it.
https://explorer.spotmecoin.com
As many of you know this is a major milestone for the project and a crucial requirement for getting listed on exchanges. We are excited and hope you are too!
https://explorer.spotmecoin.com
As many of you know this is a major milestone for the project and a crucial requirement for getting listed on exchanges. We are excited and hope you are too!
It appears 
to be working now. knock on wood.. holding rabbit foot.. crossing eyes... i mean fingers..
So I want to share what was stopping it from working if someone else decides to set up a pool.
This will fix problems with connecting to the pool
ports open.. but receiving stratum errors
and miners not getting paid.
Behavior is repeated logs of "No workers' balances reached the minimum payment threshold" even though should have.
in the cryptonote mining pool default distro you need to fix the package.json file
in package.json file
replace this section
"dependencies": {
"bignum": "*",
"async": "*",
"redis": "*",
"cli-color": "*",
"dateformat": "*",
"base58-native": "*",
"multi-hashing": "git://github.com/fancoder/node-multi-hashing.git",
"cryptonote-util": "git://github.com/fancoder/node-cryptonote-util.git"
}
With this line
"dependencies": {
"bignum": "0.12.5",
"async": "1.5.2",
"redis": "0.12.1",
"cli-color": "1.1.0",
"dateformat": "1.0.12",
"base58-native": "0.1.4",
"multi-hashing": "git://github.com/fancoder/node-multi-hashing.git",
"cryptonote-util": "git://github.com/forknote/node-cryptonote-util.git"
}
do this after you clone from git (so you have the files to edit)
and before you run npm update (so it downloads the right repository)
If you have already ran npm update.. delete node_modules folder and run again
to be working now. knock on wood.. holding rabbit foot.. crossing eyes... i mean fingers.. So I want to share what was stopping it from working if someone else decides to set up a pool.
This will fix problems with connecting to the pool
ports open.. but receiving stratum errors
and miners not getting paid.
Behavior is repeated logs of "No workers' balances reached the minimum payment threshold" even though should have.
in the cryptonote mining pool default distro you need to fix the package.json file
in package.json file
replace this section
"dependencies": {
"bignum": "*",
"async": "*",
"redis": "*",
"cli-color": "*",
"dateformat": "*",
"base58-native": "*",
"multi-hashing": "git://github.com/fancoder/node-multi-hashing.git",
"cryptonote-util": "git://github.com/fancoder/node-cryptonote-util.git"
}
With this line
"dependencies": {
"bignum": "0.12.5",
"async": "1.5.2",
"redis": "0.12.1",
"cli-color": "1.1.0",
"dateformat": "1.0.12",
"base58-native": "0.1.4",
"multi-hashing": "git://github.com/fancoder/node-multi-hashing.git",
"cryptonote-util": "git://github.com/forknote/node-cryptonote-util.git"
}
do this after you clone from git (so you have the files to edit)
and before you run npm update (so it downloads the right repository)
If you have already ran npm update.. delete node_modules folder and run again
config.json
Basically update the ports to where your server is listening, update the wallet address, and the admin password.
It is based on your configuration of the node that is running the SPOT daemon, node-js, redis, and simplewallet started in RPC mode ( ./simplewallet --config-file /path/to/spotmecoin/SPOT.conf --wallet-rpc-bind-port 8082 --password '#yeahright#' --wallet-file /path/to/your/wallet.file ). (can also put those command line switches in the config file)
{
"coin": "SPOT",
"symbol": "SPOT",
"coinUnits": 100000000000,
"coinDifficultyTarget": 120,
"logging": {
"files": {
"level": "info",
"directory": "logs",
"flushInterval": 5
},
"console": {
"level": "info",
"colors": true
}
},
"poolServer": {
"enabled": true,
"clusterForks": "auto",
"poolAddress": "PUT WALLET PUBLIC ADDRESS HERE - Basically Where you want payment to go",
"blockRefreshInterval": 1000,
"minerTimeout": 900,
"ports": [
{
"port": 13333,
"difficulty": 100,
"desc": "Low end hardware"
},
{
"port": 13336,
"difficulty": 2000,
"desc": "Mid range hardware"
},
{
"port": 13339,
"difficulty": 10000,
"desc": "High end hardware"
},
{
"port": 13329,
"difficulty": 10000,
"desc": "Hidden port",
"hidden": true
}
],
"varDiff": {
"minDiff": 100,
"maxDiff": 200000,
"targetTime": 100,
"retargetTime": 30,
"variancePercent": 30,
"maxJump": 100
},
"fixedDiff": {
"enabled": true,
"addressSeparator": "."
},
"shareTrust": {
"enabled": true,
"min": 10,
"stepDown": 3,
"threshold": 10,
"penalty": 30
},
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 25,
"checkThreshold": 30
}
},
"payments": {
"enabled": true,
"interval": 600,
"maxAddresses": 50,
"mixin": 3,
"transferFee": 50000000,
"minPayment": 100000000000,
"maxTransactionAmount": 45000000000000,
"denomination": 100000000000
},
"blockUnlocker": {
"enabled": true,
"interval": 30,
"depth": 10,
"poolFee": 2,
"devDonation": 0.0,
"coreDevDonation": 0.0,
"extraFeaturesDevDonation":0.0
},
"api": {
"enabled": true,
"hashrateWindow": 600,
"updateInterval": 5,
"port": 8117,
"blocks": 30,
"payments": 30,
"password": "UPDATE-ME"
},
"daemon": {
"host": "127.0.0.1",
"port": 19498
},
"wallet": {
"host": "127.0.0.1",
"port": 8082
},
"redis": {
"host": "127.0.0.1",
"port": 6699
},
"monitoring": {
"daemon": {
"checkInterval": 60,
"rpcMethod": "getblockcount"
},
"wallet": {
"checkInterval": 60,
"rpcMethod": "getbalance"
}
},
"charts": {
"pool": {
"hashrate": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"workers": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"difficulty": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"price": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"profit": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
}
},
"user": {
"hashrate": {
"enabled": true,
"updateInterval": 180,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"payments": {
"enabled": true
}
}
}
}
Basically update the ports to where your server is listening, update the wallet address, and the admin password.
It is based on your configuration of the node that is running the SPOT daemon, node-js, redis, and simplewallet started in RPC mode ( ./simplewallet --config-file /path/to/spotmecoin/SPOT.conf --wallet-rpc-bind-port 8082 --password '#yeahright#' --wallet-file /path/to/your/wallet.file ). (can also put those command line switches in the config file)
Code:
{
"coin": "SPOT",
"symbol": "SPOT",
"coinUnits": 100000000000,
"coinDifficultyTarget": 120,
"logging": {
"files": {
"level": "info",
"directory": "logs",
"flushInterval": 5
},
"console": {
"level": "info",
"colors": true
}
},
"poolServer": {
"enabled": true,
"clusterForks": "auto",
"poolAddress": "PUT WALLET PUBLIC ADDRESS HERE - Basically Where you want payment to go",
"blockRefreshInterval": 1000,
"minerTimeout": 900,
"ports": [
{
"port": 13333,
"difficulty": 100,
"desc": "Low end hardware"
},
{
"port": 13336,
"difficulty": 2000,
"desc": "Mid range hardware"
},
{
"port": 13339,
"difficulty": 10000,
"desc": "High end hardware"
},
{
"port": 13329,
"difficulty": 10000,
"desc": "Hidden port",
"hidden": true
}
],
"varDiff": {
"minDiff": 100,
"maxDiff": 200000,
"targetTime": 100,
"retargetTime": 30,
"variancePercent": 30,
"maxJump": 100
},
"fixedDiff": {
"enabled": true,
"addressSeparator": "."
},
"shareTrust": {
"enabled": true,
"min": 10,
"stepDown": 3,
"threshold": 10,
"penalty": 30
},
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 25,
"checkThreshold": 30
}
},
"payments": {
"enabled": true,
"interval": 600,
"maxAddresses": 50,
"mixin": 3,
"transferFee": 50000000,
"minPayment": 100000000000,
"maxTransactionAmount": 45000000000000,
"denomination": 100000000000
},
"blockUnlocker": {
"enabled": true,
"interval": 30,
"depth": 10,
"poolFee": 2,
"devDonation": 0.0,
"coreDevDonation": 0.0,
"extraFeaturesDevDonation":0.0
},
"api": {
"enabled": true,
"hashrateWindow": 600,
"updateInterval": 5,
"port": 8117,
"blocks": 30,
"payments": 30,
"password": "UPDATE-ME"
},
"daemon": {
"host": "127.0.0.1",
"port": 19498
},
"wallet": {
"host": "127.0.0.1",
"port": 8082
},
"redis": {
"host": "127.0.0.1",
"port": 6699
},
"monitoring": {
"daemon": {
"checkInterval": 60,
"rpcMethod": "getblockcount"
},
"wallet": {
"checkInterval": 60,
"rpcMethod": "getbalance"
}
},
"charts": {
"pool": {
"hashrate": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"workers": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"difficulty": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"price": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"profit": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
}
},
"user": {
"hashrate": {
"enabled": true,
"updateInterval": 180,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"payments": {
"enabled": true
}
}
}
}
So.. its fixed. wasn't a port problem per se... more of a wrong url for the node supporting the mining in the website config.
pool1.crypto-me.com isn't responding on port 13330 ().
pool1.crypto-me.com isn't responding on port 13331 ().
pool1.crypto-me.com isn't responding on port 13332 ().
pool1.crypto-me.com is responding on port 13333 ().
pool1.crypto-me.com isn't responding on port 13334 ().
pool1.crypto-me.com isn't responding on port 13335 ().
pool1.crypto-me.com is responding on port 13336 ().
pool1.crypto-me.com isn't responding on port 13337 ().
pool1.crypto-me.com isn't responding on port 13338 ().
pool1.crypto-me.com is responding on port 13339 ().
pool1.crypto-me.com isn't responding on port 13340 ()
Correct address for the configuration has been updated from pool.crypto-me.com to pool1.crypto-me.com
pool1.crypto-me.com isn't responding on port 13330 ().
pool1.crypto-me.com isn't responding on port 13331 ().
pool1.crypto-me.com isn't responding on port 13332 ().
pool1.crypto-me.com is responding on port 13333 ().
pool1.crypto-me.com isn't responding on port 13334 ().
pool1.crypto-me.com isn't responding on port 13335 ().
pool1.crypto-me.com is responding on port 13336 ().
pool1.crypto-me.com isn't responding on port 13337 ().
pool1.crypto-me.com isn't responding on port 13338 ().
pool1.crypto-me.com is responding on port 13339 ().
pool1.crypto-me.com isn't responding on port 13340 ()
Correct address for the configuration has been updated from pool.crypto-me.com to pool1.crypto-me.com
Great comments so far guys.
No issues with the servers.
And it is cryptonote based so tools / mining strategies based on crypto note will work well.
We are working on a pool as well. We havent verified the tools yet, but feel free to connect to it and try it out. Good way to see network hashing rates.
http://pool.crypto-me.com/
If others are interested in setting up a pool, we can share a sanitized version of our config.json if there is interest
No issues with the servers.
And it is cryptonote based so tools / mining strategies based on crypto note will work well.
We are working on a pool as well. We havent verified the tools yet, but feel free to connect to it and try it out. Good way to see network hashing rates.
http://pool.crypto-me.com/
If others are interested in setting up a pool, we can share a sanitized version of our config.json if there is interest
This happens when the simplewallet is opened and not exited properly
You need to delete the blockchain data store. and then resync the wallet to the blockchain. Do not delete your wallet or you will lose everything.
Sent this to another user...If it doesnt work or need some help let me know
ok, the way I was able to replicate the issue, was that the wallet had been opened and was left open. It had been recieving notifications and another instance of the wallet was opened, which opened from the last saved state.
The two instances working on the same wallet file screwed things up.
So to fix this
we are going to force reloading the blockchain of the node.
Step 1) --stop all instances of the node, wallet, miner
Step 2) Find the directory where the blockchain is stored and delete it
Important (do this on the computer where you open your wallet)
On windows
It should be under your app data folder. This is a specific folder to your computer. Generally located in the path below
C:\Users\your-logged-in-user\AppData\Roaming\SPOT
On linux/mac it should be in your profile directory under the folder .SPOT
3) Next start up the SPOT network node
let it syncronize
Once Syncronized -> Open the wallet and type reset which will reread the entire block chain.. not just where it last left off.
that will give you every block that was sent to your wallet
You need to delete the blockchain data store. and then resync the wallet to the blockchain. Do not delete your wallet or you will lose everything.
Sent this to another user...If it doesnt work or need some help let me know
ok, the way I was able to replicate the issue, was that the wallet had been opened and was left open. It had been recieving notifications and another instance of the wallet was opened, which opened from the last saved state.
The two instances working on the same wallet file screwed things up.
So to fix this
we are going to force reloading the blockchain of the node.
Step 1) --stop all instances of the node, wallet, miner
Step 2) Find the directory where the blockchain is stored and delete it
Important (do this on the computer where you open your wallet)
On windows
It should be under your app data folder. This is a specific folder to your computer. Generally located in the path below
C:\Users\your-logged-in-user\AppData\Roaming\SPOT
On linux/mac it should be in your profile directory under the folder .SPOT
3) Next start up the SPOT network node
let it syncronize
Once Syncronized -> Open the wallet and type reset which will reread the entire block chain.. not just where it last left off.
that will give you every block that was sent to your wallet
very very hard...