keep up the good work  btw, u have any suggestions for antminer s7 setup? they are hanging from time to time and i have to manually reboot them...it happens on all dgb pools  I have 1x S7 mining at PPLNS and 1x S7 mining at SOLO. About once a 1-2 weeks it loose 1 hashboard and I reboot it. After reboot it keep mining at full speed. Antminer firmware is not for DGB, this is not pool issue. --- Your average reward per 1 TH/s per 1 day (DGB/1THs/1Day) for the last:
24 hr period: 13.63630566 DGB (0.00004895 BTC*)
3 days period: 12.38484574 DGB (0.00004446 BTC*)
7 days period: 13.55614922 DGB (0.00004867 BTC*)
14 days period: 13.49420185 DGB (0.00004844 BTC*)
BTC* - at current DGB/BTC rate (Poloniex)
BTC PPS = 0.000041 DGB/BTC = 0.00000359 |
|
|
|
|
DGB profit depends much on its DGB/BTC rate as well as time of exchanging this. SHA256 altcoins depends on BTC network difficulty as well and it can no be much more profitable at the time of mining but it can be later. This is the only reason to mine DGB instead of BTC.
There is no any pool which can bring at least +10% from nothing, on the long time range most of them has equal profit except some technical tricks and advantages which allow good pools to be one step forward of others in compare with junk mining pool "from the box".
And there are a lot of issues calculating what is profitable and what is not.
During last months rate was about 0.00000250 BTC and if someone exchanges each his 1 DGB to BTC - its his deal. But now rate is 0.00000280+ for at least one week, it is good chance to convert everything mined at -250 and have at least +10% in BTC.
If you are holding DGB and do not care about current rate, in this case dgb256.online one of the best options. And I am miner from the beginning but not just pool owner and I know exactly real mining profit, but not WhatToMine virtual numbers.
Absolutely each pool has bad luck periods but it has good luck periods as well. Posted mining rewards examples above.
And my previous post was in support of miner above, I've checked and found that he is a real person who are mining on the pool right now (according to nickname).
So if you got small profit for a 7 weeks on both PPLNS and SOLO - you may think so, I do not argue. But my numbers and my statistics tell me positive situation.
BTW recently I've calculated all work diff for all found blocks in compare with network diff of found blocks from the pool start time and it is 102% luck of 100%. So each miner from the beginning got at least +2% in compare with some other pools. And we got these 2% not from the nothing, it means that some pools got only 98% roughly, they lost orphan competitions or they are slow on a junk $5 VPS servers or not perfectly tuned or configured.
This is only my opinion and I do not force anyone to believe.
But person above also left his feedback and no reason for doubts here except he is newbie forum member.
That is his opinion even if this person wrong in someone eyes.
|
|
|
|
Really? How long have you been mining there?
I do not know this guy in a person and I do understand how usually looks like message from just registered newbie forum member, but meanwhile some guy with the same nickname is actually mining at the pool for the present moment, stats here https://dgb256.online/index.php?k=stats and he found more than 100 blocks https://dgb256.online/index.php?k=userinfoNo reason for me to post kind of fake feedbacks, pool has stable hashrate and more than 50 pages support thread at another forum for 1.5+ years of mining. So I ask you to refrain from any provocations and use this topic as a technical one and pool-related but not flood and talks like this. |
|
|
|
Nicehash support added to SOLO pool Word nicehash should be used as a Password for Nicehash use. Example URL: stratum+tcp://solo.dgb256.online:8888
Worker: DLMj5oMNKyQ3kAcigFReu5YfaC35dENkaq (replace to your DGB address)
Password: nicehash |
|
|
|
|
Some users specify custom fee instead of automatic maybe in way to save some because of high BTC rate.
I highly recommend to keep Automatic Fee mode ON, because in the Double-spending process it is neccessary to have good and actual Network Fee in the new transaction, so any Mining Pool should want to take this new transaction and prefer it over others transactions in the queue.
So please think twice if you are using manual fee mode!
|
|
|
|
|
Sorry but this service is not the best solution for small BTC amounts, especially now with extremely high network fee for last 2 days. You can not pay network fee and service fee from your amount.
Anyway service works flawlessly.
|
|
|
|
|
One more node is up and running, 6 broadcasting nodes total all over the World:
- New York
- San Francisco
- Canada
- Germany
- Singapore
- China
It provides a lighting fast delivery of a new double-spending transaction to miners, so as result much more chances to make successful double-spending than just pushing tx via local bitcoin client or public PushTX services.
|
|
|
|
Tsk, a double-spending tool not for dummies but for dummy scammers. People should really stop making these shitty things as they don't really have any practical legal use. They are more used for scams than it is used for legitimate purposes. Then these sites place the wordings like "this is for education purposes only" but they well know that it is being used for scams!
What are you talking about? What scam? This is a real way for recovery Stuck coins in 99% of cases and this is not scam and nothing illegal here. As soon as you own Private key - these are your coins. But if someone silly enough and accepting 0-confirmation transactions - that is problem of those guy, but not Bitcoin and Double-spending. Study technology and you will not have any problems. |
|
|
|
|
Minimal service fee lowered to 0.0001-0.004 for small transactions. Do not forget to Verify before broadcast.
|
|
|
|
|
Automatic network tx fee calculation value increased from +20% to +30% from bitcoinfees.21.co recommended fee because of high BTC network load and huge mempool size and this is still intensively growing.
Manual mode still available, you may uncheck it and use whatever network fee you want.
But please do not even try to doublespend it now with low fee - it will stuck again as previous unconfirmed transaction.
|
|
|
|
You may create your own service on home PC and not paying for several dedicated servers with full nodes and not paying for developing anything and create double-spending transaction by hands with your own knowledge and pay nothing. Then you will try to send New TX using public well-known PushTX services https://en.bitcoin.it/wiki/Transaction_broadcasting or own Bitcoin Core and got mempool-conflict error and that's it. And if it sent in a half times it will be dropped by other peers. But it is Free. And most of the time this is useless especially if transaction quite "fresh" and recent. Accelerations services are also free and it guarantee nothing. This service is not for $10 or 0.001 transactions, but in case 1-5-10 BTC stuck it will be acceptable to someone to pay % for recovering coins and not wasting time. Especially now during lighting fast BTC rate growing 5%+ per day. Smaller amounts are also works but percent rate will be higher and this may not be acceptable for everyone. It might be good idea to count your own coins but not others. Nobody forced to use this service. Too much? Just ignore this. GL. |
|
|
|
|
One more custom rebuilded Bitcoin Full Node added to the service for even faster TX distribution.
Double-spending TX distribution schema improved.
Also changed input selection algorithm for transactions with multiple same addresses.
|
|
|
|
I would rather use wallet which support RBF, ask receiver to use CPFP if possible, rebroadcast my own confirmation transaction by myself or simply use free service which ask less information or worst case i would make exact same transaction with bigger fees.
Honestly, i don't see any purpose of this website/services.
Ok, just passing by and that's it. This is not for you. Looks like you never did double-spending yourself and even not understand some details especially talking about rebroadcasting "your own confirmation transaction". And even if you are able to make the same transaction with higher fee, you have very low chance to distribute it in the Network without special tricks. |
|
|
|
I remember there was an old site that essentially did the same thing, apart from i think you don't actually hold your private keys. Link is here but seems to be down at the moment. Is your service essentially the same as that site's? As regards to using this to commit fraud, these days not many sites even accept zero conf transactions even with high fees anymore. nobody is dumb enough to accept 0 conf transactions. So its not really an issue. I do not know what exactly those service does and I am not related to those service. My service is not hold Private Keys and anyone with basic JavaScript knowledge may check and proof it. Service use BTC Address (extracted from Private Key in user browser), previous TXID and New address and New fee to generate a new transaction at server side. After this it returns new Unsigned double-spending transaction back to User Browser and sign it inside user browser by JavaScript. It is based on well-known Coinbin JS client, you may check whole https://txid.io website , this is a fork of Coinbin with some improvements and this is open source as well. The only one thing at server side - generating new transaction, because I do not offer this as free service for own reasons. |
|
|
|
- New transaction will be broadcasted to BTC network (repeatedly until confirmed) via our own specially configured nodes (no 258: txn-mempool-conflict error)
.. to broadcast new transaction repeatedly until confirmed... Most of full nodes in Bitcoin network i.e. Bitcoin Core configured by default and they will not accept double-spending transaction, because they do already have this Input spent in their mempool (original transaction) and they assume that these coins already spent. And this is correct. They will accept new double-spending transaction only when previous one will be expired and removed from their mempool. But there are a lot of nodes in the network and not each of them has original transaction, also some of nodes are restarting and there some new nodes started after original transaction was sent. So these nodes do not have original transaction in their mempool and they accept doublespending tx and will relay it to all peers and some peers will also accept it and relay. The only way to spread double-spending transaction to the network in the fastest way - to send it repeatedly with some intervals to a lot of peers (not just to standard 8 peers) to have a chance to fill their mempool with a new transaction. Everybody can create double-spending transaction manually without any services (sure you need advanced knowledge to do it) or even Bitcoin Core client can be used with some options, but this is just a half of the solution. Another half is to broadcast new transaction and sometimes it can be much more difficult than create it. |
|
|
|
Looks like a nice tool but people at this point should really be using wallets that support RBF. Double-spending is an outdated solution by now.
You are correct, smart people do it or they can calculate correct fees and got it confirmed within 1-2 blocks. But there are a lot of people who do not care about fees at all. And also some online services and wallets put wrong fee amount, i.e. blockchain.info . But if private key exportable - it can be used for doublespending. There are also some other ways to accelarate stuck transaction like using CPFP when it possible or use some 'accelerators' but this not guaranteed. Double-spending is the most complex solution but it 100% working without doubts. The main issue what time it takes to deliver new transaction to miners. |
|
|
|
|
Show Posts
