 Show Posts
|
|
Pages: [1] 2 »
|
anna ask, is there will be available mobile wallet soon?
Yes ! With some luck we will make it available in beta within the next two weeks. I have the android wallet working and made the first payment with it yesterday. It uses viewkey synchronization and anyone who has used the sumokoin wallet (which I launched months ago) or moneroju will highly appreciate the gained performance in synchronization (and extreme data usage reduction). Running a wallet against a remote node that is outside your control always comes with a risk. We have setup a wallet node for OMB users to synchronize against but everyone is obviously free to setup their own wallet node (which is simple and documented) to use it with the mobile wallet. Stay tuned! Edit: s/if/is/ |
|
|
|
It's a matter of priorities but I admit we dropped the ball here. The best decision was to close out the pool. This wasn't run by the devs as a group. It was just run by me personally. The pool had a bug that caused it to accumulate a 100K OMB backlog which I'm paying out of my pocket to get all miners payed. Going forward we recommend to use the nodejs-pool code instead of cryptonote-pool. All: we're going to terminate pool.ombre.io, which has been a problem child from the start, in favor of the other (more stable) pools available. The dev team simply does not have enough time to deal with pool management in addition to development of new features and helping with technical issues.
It will be closed within 24 hours so please migrate your miners to a different pool
All pending balances will be payed out.
Devs not being able to keep a pool running decently sounds weird to me lol |
|
|
|
|
All: we're going to terminate pool.ombre.io, which has been a problem child from the start, in favor of the other (more stable) pools available. The dev team simply does not have enough time to deal with pool management in addition to development of new features and helping with technical issues.
It will be closed within 24 hours so please migrate your miners to a different pool
All pending balances will be payed out.
|
|
|
|
Thank you for confirming on Telegram that you have been payed. The casi addresses are not supported by the official pool which is why you had a delay in the payment. This was also announced in the telegram group but you seem to have missed this. You were banned because you were spamming the telegram group. Next time please try to be a bit more patient. Yeah when told dont pay offical pool.. ban me telegram group.. |
|
|
|
|
::::::: Small dev update!
Hey folks! We have planned the following work for the upcoming 4 weeks:
Create a wallet node & release the Android wallet beta version
We are making progress with the Android wallet and plan on releasing a test version within two weeks (plain APK) and a beta version within 4 weeks (play store). We enhanced the ombred daemon so that wallets can provide the node the viewkey and let the node only return blocks that have transactions for the viewkey during sync. This drastically reduces the sync speed and data consumption by a 100x. However this approach does give a lot of trust to the wallet node and so we will likely make this synchonization method option so users can chose to sync with or without viewkey.
Owner: @sadbatman
Enforcement of authentication between GUI wallet and wallet RPC daemon
The GUI wallet runs the wallet RPC daemon in the background. There currently is no authentication enforced by the wallet RPC which is a security issue. We will extend the RPC daemon and GUI wallet to enforce proper authentication.
Owner: @crypto_sr
Whitepaper on [Suspicious link removed]pression
We think there is a lot to be gained with [Suspicious link removed]pression and will research this topic by writing a whitepaper that also takes things like bulletproofs into account.
Owner: @crypto_sr
Wiki bounties
We created a wiki and would like to collect the knowledge within the community in written form. We will create bounties for people to write wiki articles on topics such as, how to recover your wallet, how to export import a block chain, how to run a testnet, etc
Owner: @bluecore
So stay tuned and we'll give an update on progress within two weeks!
|
|
|
|
|
Our hardfork to cryptonight heavy and larger transaction sizes was a success ! Now we'll focus on releasing the Android wallet.
We also release 1.4 which is available for download now. This release fixes a lot of the synchronisation issues people were having.
|
|
|
|
It’s interesting to see the progress of this project  But I can't download the wallet  Why can't you download the wallet ? |
|
|
|
seems that ombrepool.com is on a different blockchain?
They didn't follow the fork?
What pools are on the right chain?
pool.ombre.io is on the right chain. The new binaries also have updated checkpoints to counter the current split. Regarding that current blockchain split. We have a block time window of 60 seconds and it makes it easier for these splits to happen. We have seen splits that exceed 100 and this is unacceptable since they really should not exceed the amount of confirmations needed for transactions and miner rewards. We therefore will now focus on changing Ombre to prevent splits like we have seen this weekend. This will be the high priority focus for us devs in the next week. |
|
|
|
The Thunder release is out: https://github.com/ombre-projects/ombre/releases/tag/1.3This release contains many changes and bug fixes. Highlights are: - Hardfork to change to cryptonote heavy - Increased transaction size - Proper DNS checkpointing - Additional wallet key protection - A new RPC in the ombred which allows synchronisation with the viewkey (will be used in android wallet). All users should upgrade in the next few days. |
|
|
|
Update from the devs. The official pool is back up and running. We took measures to make sure it won't be down again. Right now we are working on the following items: - Updating the PoW to make it asic resistant. We will likely follow the Monero implementation but have not made a decision yet. @crypto_sr is the owner of this task
- Increasing transaction sizes (see also https://github.com/ombre-projects/ombre/pull/34/) as some large transactions get blocked by this. @sadbatman is the owner of this task
- Implement an Android wallet (@sadbatman is the owner)
We also made a prerelease last week available here: https://github.com/ombre-projects/ombre/releases/tag/1.2.1aThis is an experimental release and please only use it when you are willing to give use feedback on bugs & issues. The prerelease contains the following changes: - Fixed DNS checkpointing: we now have DNSSEC servers running for this.
- Enable HTTP compression on RPC communication.
- Enforce (and recover) strict file permissions on wallet files.
As always - please report problems on github or come hang out in the Telegram group. |
|
|
|
Hey all, Just a reminder that we really appreciate it when you report issues you run into on our GitHub repo. https://github.com/ombre-projects/ombre/issuesNo matter how small: any bug or suggestion helps! Also note that we are looking into implementing a hardfork to deal with the ASICs and additionally we're preparing the Android wallet. Cheers! |
|
|
|
Small updates: 1) An updated version of the block rewards over time (emission) can be viewed here: https://www.ombre.io/emission.jpg The first block is low because it was the genesis block with 1 OMB as the reward. 2) Stocks.exchange mentioned we will go live tomorrow. Today the wallet was tested and verified to work correctly. |
|
|
|
Hmmm...it seems a cheerleader is oblivious to the fact that just like most crypto project, Sumo is open source. Heck, it's literally a copy of Monero for chissake which is truly and idealistically an open source and decentralized project at its very core. That means it's anybody's business if they so choose to participate in whatever manner...unless, of course, the cheerleaders and their bosses are actually making this their own pet project for their own personal benefit in the guise of being open source to camouflage their true intention; and the rest of us are regarded by them as expendable. So when a cheerleader tell off a participant of their "supposedly" open source project to "mind his business" and stay away from their pet project, it's actually a Freudian slip of their true intention.
Cases in point:
1. The exorbitant Sumokoin premine of 10% of the coin supply (about 9 million coins thereby eventually enriching themselves)
2. cheerleaders behaving like a pack of rabid dogs ganging up senselessly on even the slightest of criticism of their pet project that would eventually enrich them like nobody's business.
@Visdude ... you should not say that here. The sumokoin folks don't like other people asking questions about the premine. Be careful... And question like that will be met with the iron fist of FUD. But you got to give the Sumokoin folks (if there is more than one) one thing... they did manage to pull it off... either for the sake of sumokoin or personal benefits. Although there is one thing that's actually very true... they do need help. Commits on Sumokoin (core) are a scarce commodity and I would claim that maybe 99% of the code base is identical to monero's code base (2016/2017 version). Some packages renamed, a few changes here and there...but if you use a good tool to compare both, you might be surprised. https://github.com/sumoprojects/sumokoin/graphs/code-frequencyI think it's more than 99% but you don't see it in the code-frequency because a lot of changes to the monero code were incorporated in the initial commit on github. This code frequency graph also doesn't show the work that is done on the other sumokoin repositories. The devs favor doing development in their own branches and pulling big changes into the sumokoin code base. |
|
|
|
I have a question and I hope that someone can help me out. I installed this pool and everything seems to be running right except for the wallet RPC perhaps? In the admin panel I get fail and the error is { }. (Note, that there isn't an error descriptor between the brackets) It is driving me nuts because I don't even have search terms to look for a solution. I will try to give ya as much info as I can: I have the blockchain synced, the wallet RPC going (at log level-2) and just showing green and blue info/blocks received ...etc, and I can connect miners to the pool. When I have the RPC going and go to my admin page I get this error:  The wallet RPC does not hang and continues to refresh INFO and DEBUG info. {
"coin": "Monero",
"symbol": "XMR",
"coinUnits": 100000000,
"coinDifficultyTarget": 120,
"logging": {
"files": {
"level": "info",
"directory": "logs",
"flushInterval": 5
},
"console": {
"level": "info",
"colors": true
}
},
"poolServer": {
"enabled": true,
"clusterForks": "auto",
"poolAddress": "44XjW8cg418JmtooiVgKzUCnQFbMEzkFtD1mW2fqDCQSgv5hok4QfZzQuRCKWydkrYik8Vj3VaLc22zLDFRW7EtDJyGS6jR",
"addressBase58Prefix": 18,
"blockRefreshInterval": 1000,
"minerTimeout": 900,
"ports": [
{
"port": 3333,
"difficulty": 100,
"desc": "Low end hardware"
},
{
"port": 5555,
"difficulty": 2000,
"desc": "Mid range hardware"
},
{
"port": 7777,
"difficulty": 10000,
"desc": "High end hardware"
},
{
"port": 8888,
"difficulty": 10000,
"desc": "Hidden port",
"hidden": true
}
],
"varDiff": {
"minDiff": 2,
"maxDiff": 100000,
"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": 5000,
"minPayment": 3000000,
"denomination": 1000
},
"blockUnlocker": {
"enabled": true,
"interval": 30,
"depth": 60,
"poolFee": 0.45,
"devDonation": 0.001,
"coreDevDonation": 0.001,
"extraFeaturesDevDonation": 0
},
"api": {
"enabled": true,
"hashrateWindow": 600,
"updateInterval": 5,
"port": 8117,
"blocks": 30,
"payments": 30,
"password": "xxxxxxxxx"
},
"daemon": {
"host": "127.0.0.1",
"port": 18081
},
"wallet": {
"host": "127.0.0.1",
"port": 8082
},
"redis": {
"host": "127.0.0.1",
"port": 6379
},
"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
}
}
}
} I tried binding a different port in the command line and making sure it was also set in config.json wallet area and forwarding that port all to no avail. Can anyone point me to help? With the lack of information for the error it is making researching it near impossible. What would the error { } mean? I have looked at many related posts. I can duplicate their errors and resolve them (ERRCONNECT..etc) using 127.0.0.1 in the wallet area and bind that ip and port 8082 to the wallet but I get the { } error and the fail still. If someone could help me out I would really appreciate it. It is just so weird that it doesn't describe the error (I.E. "syscall" etc.) Did you resolve this already ? If not then (as root) run "netstat -anp | grep wallet-rpc" and compare the port with the port in your pool config. |
|
|
|
After 6 hours at 500 H/s only have 5 OMB. Why a newborn coin is so difficult to mine?
You have to keep in mind that when a block is found there are two delays before you receive money: - First the block needs to mature. You can see the progress of that in the blocks page.
- Second the pool payment process needs to run.
I assume that since you posted this you received more coins ? |
|
|
|
Hi,
No exchange yet ?
Not yet but we are working on it! |
|
|
|
|
Thanks for reporting and please ignore the hardfork warning. I will get rid of it with an update later today or tomorrow.
|
|
|
|
|
Small update:
The seed nodes are up; the explorer is up and the pools are running.
We did a quick bugfix release of the CLI tools as a libcrypto shared library dependency sneaked into the release. This dependency should not be there and could prevent some users from using the CLI tools.
Right now we are looking into some issues that were reported with the GUI wallets.
|
|
|
|
|
Hey all. We are currently setting up the seed nodes and enabling the pools. We didn't do this before the announce (on purpose) so that everyone has a fair chance at mining the coin.
Stay tuned they will be online in the next 30 minutes.
|
|
|
|
|
