Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 736. (Read 1260636 times)

@Danbi
Finally got around to setting up an Ubuntu 14.04 LTS box and compiled wallet 2.0.3 diamond-qt
Where do I find the datadir so I can add diamond.conf ?

If you are/were mining on danbi's Pool on 2014-08-02, you should take note of this.

During the wild forks that were happening at that time, the danbi's Pool backend scripts managed to stop. This is an extremely rare event, has happened once or twice before for the pool's history. This time however, I was (very) away from computers and could not react soon enough. In addition, the data inconsistency was more than the MPOS automatic accounting scripts could handle.

As a consequence, all the shares submitted during that time were assigned to one block, and all the next blocks (636 in total) were not accounted properly.

What is most interesting, nobody, but community member hallared ever contacted me on this matter. One would think, that you gals and guys don't need the Diamonds you mine at the pool? ;-)

In this particular case, hallared not only showed interest, but in fact helped me great deal in actually deciding on a fair distribution of these unaccounted coins. Big thanks to hallared from me!!!

I have now executed the scripts that will send out the amounts miners were supposed to get. It is sent from the pool's hot wallet, but will not be recorded in the pool's statistics/transactions. That was something I contemplated doing, but it turned out to be too much of doctoring the database and could lead to worse situation.

If you mined at danbi's pool between blocks 513651 and 514538, you should receive your missing earnings with an transaction message of "lost coins from danbi's Pool blocks 513651-514538".

If you believe you had mined at danbi's Pool during that time, but your calculations/expectations to not match what was sent, or you received nothing, please contact me to sort it out.

I am sorry for the inconvenience this situation may have caused you.

Please note you may have more than one address in your wallet!

Some addresses are created automatically by the wallet when sending and there is change remaining.
The safest way to find all of the addresses is to use the 'listaddressgroupings' RPC/console command.
You need to save the private key for each and every one of the addresses that have non-zero balance! Otherwise, you will lose those coins for good.

This is a nasty feature of the bitcoin protocol. An upcoming wallet release will have additional tools to deal with it. For now, you could use Coin Control to send the change amount to one and the same address -- but that is too much manual work and will only affect new transactions.

first of all make sure ur wallet version is at least 2.0.3.0 (soon 2.0.3.1 release can be expected)
u can sync with ur old wallet.dat

all mining minting and incomming/outgoing transactions that where orphan or done in a wrong for will  after sync be visible as unconfirmed

coins stuck in such a unconfirmed transaction u can claim back by repairwallet command in console

a bit more complicated would be the methode mullick suggests (2nd level cryptsy support)
i just post it here but never tryed it myself follow his guide at own risc.

regarding TX ID thats are not visible at blockexplorer they didnt happen on main chain
if cryptsy wallet was sometime on wrong fork chain only cryptsy support answer and also the way how they plan to fix that
(resync on right chain and repeat transaction i guess...)

So i've resynced using my old wallet and it's now showing the minted transaction i did at the end of it. However it's missing the transaction i sent to my address a few hours before the minting.
If i dump my priv key and reload the chain do i place my wallet back in the roaming folder before i sync or do i let it fully sync with fresh wallet then import my privkey afterwards?
The txid i have from cryptsy does not exist on the blockexplorer.
Is there a way of checking to see if it has been sent to the forked version?

My pleasure!

u are a year to late  
but lucky u block rewards still the same until total coins reach 1 000 000  

Oh that I know, but it's important to have solo-mining down because the best time to mine a coin is right when it's released.  I also like to know the all of everything, I'm a very curious cat.

And just now, 30 minutes after the first one, ping! 

Yeah, I was expecting it to take a few hours to show up.  Did wanna know what I could do for more info though, thanks for the tips.  Oh, and thanks loads for the config file.  Um... with this many forks, variants, optimized versions, one can easily lose track of what's where when cutting and pasting bits from here and there, and that's what happened here.  Got it all ironed out and shortly thereafter, ping!  Saw a diamond arrive in the wallet and Sgminer was all proud of itself.  No tip-bot here but have a bumper-sticker I made way back when I worked for an ISP.  My boss really hated this.  Thanks again!

http://i33.photobucket.com/albums/d72/AtomicNixon/Graphics/IReadYourEmail.gif

If someone has ended up in the "disconnect game", and sees the "not enough work" message in their logs, you are good candidate to test the next wallet version, which might fix it for you. Although the fix seems safer now, we would like to verify it on more real-world cases.

Please contact me via PM. We presently have Windows and Mac wallets compiled with the fix.

atomiccat ur solomining settings seems to be ok

thats my output when i force it mione at local wallet because u set wrong password for pool
as u can see it show WU 0.000 at solo mining thats normal as u can see i use -T option so u see more details

if u do solomining u get no feedback from miner beside when u find a block and that can take a few hours or more .....
if ya do solomining with a backuppool u will see the diff adjustments and new block found messages form pool stratum regulary

i use the miner u can find at http://bit.diamonds/mining.html

u said 14 mhash is ur mining power thats at actual diff a handful like 4-5 DMD a day
but at solo mining randomness and luck kick in full
so its still possible have a day and mine zero
and have another day mine 10 dmd.....
over longtime the average will be same as pool mining.........

on dmd multipool miningstats u can see something like
Confirmed BTC: 0.05455470 (at least thats my mining stats   )
confirmed BTC are BTC u mined which are already arrived at our multipool and wait for being converted towards DMD

so this days u will see this number grow as a sign ur mining works fine
as soon as we reactivate the cryptsy api engine the automated conversion will start again

people with low mining power will see somedays no increasement in confirmed btc because wafflepool and nicehash only payout after the mining BTC is bigger than send trigger level i think once a week they send our even smaller pieces

couple things,

1. Where can DMD coins be sold as of now as cryptsy doesnt work for them (yes they know).

2. Someone explain minting to me like im a 3 year old!

Does the number of coins in the wallet effect how much minting happens ?
How much can you get for minting ?

thanks!

I would guess you could look in the logs see what the wallet is doing network-wise. You could actually add the "debug=1" option in the .conf file to have more info, but that is just debug info. If you want to know how the wallet is working with the network and with your miner, go into the wallet console and type "help" you will get all possible commands (gethashespersec or getgenerate are 2 among many others). Also try using verbose mode in sgminer. You will see more information on what is happening behind the scene.

I can't solo-mine with sgminer anymore because I've upgraded to nvidia cards now, so I don't have screenshots.

EDIT: and look how partially lucky you are: https://bitcointalksearch.org/topic/m.6646488 - Partially because I didn't paste all the sgminer output at that time, but it should give you a good start.

Now that I am looking at the batch file the diff multiplier had to be deactivated when solo mining. Try taking it out but Danbi has just confirmed to me that it actually doesn't matter whether it's there or not as with getwork there is no such thing as difficulty.

You know what, why don't you post here your sgminer output. A screenshot would make it easier to troubleshoot. Please make sure there is no error message when you startup sgminer. If there is, please also post it here.

Finally but actually most importantly, and I quote from Danbi:

"solo mining with 16 Mhash/s will produce DMD in long intervals
unlike with pool mining, you only submit work when you found a block
so a long row of 'no shares' is perfectly ok
then suddenly, BLOCK fond
as sgminer can't find out whether it is talking to a wallet to an pushpool server, it can't show different interface"

Thanks.  I figured the --server flag would be a redundant redundancy issue, no big.  I'm quite confident it's all set up right, it's just the lack of feedback and info that's tweaking my info-hungry brain.  If the wallet is acting as a local server there should be a way of finding out what it's processing, what work it's sending and receiving.  This is such a new scene and there's a million n00b just getting started guides, but very little in-depth write-ups.  Q flag is important, but I'll strip a few things down and see if behavior changes.  That's usually my first step as well.  Oh, don't suppose you'd have a screen-shot of what Sgminer mining solo properly looks like?  Using the Diamond fork and getting a solid 16,000 Kh/s on Danbi's pool.  Thanks in advance for any info.

DMDcreeper. No his batch file is configured properly. The first pool is set to 127.0.0.1. Digsys pool is the failover pool

--------------

Atomicat,

I recommend you start with a very simple batch files. Take out everything non essential (failover, Q flag, td, lookgap) except the multiplier of course. BTW when I used to solo mine I didn't use the --server flag while launching diamond. I believe setting it in the diamond.conf files as (server=1) already does the job.

BTW which sgminer are you using?

I will revert with more info later on as I am at work and if no one else has properly resolved your issue.

Atomicat,

Your config file is setup like you are solo mining on the same machine as your wallet.  But your batch file indicates you are connecting to the digsys pool. What are you trying to do?

Ok, I give up.  I figured Diamond would be a good coin to try solo mining.  Enough hash to keep the network up, but difficulty slightly lower than Bitcoin.  What eludes my google-fu is what console commands in the wallet will give you any feedback on how my mining is going.  Be we crunching blocks or just spinning our wheels?

My diamond.conf file...

rpcuser=Atomicnixon
rpcpassword=JesusBuiltMyHotrod
rpcallowip=127.0.0.1
rpcport=17772
addnode=213.229.0.41
addnode=193.77.159.166
addnode=113.168.158.16
server=1
listen=1
daemon=1
gen=1


Sgminer batch...

sgminer.exe -k diamond -Q 50 -o 127.0.0.1:17772 -u Atomicnixon -p JesusBuiltMyHotrod -o stratum+tcp://dmdpool.digsys.bg:3333 -u xxxxxx -p x --xintensity 300 -g 1,2 --thread-concurrency 8192,16384 -w 256 --lookup-gap 0 --difficulty-multiplier 0.0039062500

Getmininginfo...

{
"blocks" : 519112,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 41.25975732,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 364547,
"networkhashps" : 2710658635,
"pooledtx" : 0,
"stakepower" : 0,
"testnet" : false
}

In sgminer it shows me connecting to pool 0, sets difficulty via longpoll correctly, then shows nothing but a string of "Network difficulty set" and "Stratum from Pool 1 detected new block.  Shows 0 for accepted/rejected blocks.  One other minor thing... GPU-0 is showing WU:0.137/m but GPU-1 shows 0.000.  Can someone fill in some detail for me here?

Edit: Didn't miss running wallet like so:

C:\Mining\diamond-qt.exe --server

cryptonit,

Just wondering if you know when my first weeks DMD mining payment will come to me?  Are you holding off due to Cryptsy exchange issues?  If so no biggie.  I understand.

Thanks,

pokeytex

X13 re-enabled on wafflepool