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

the short answer:

any transaction set coin-age of the involved coin pile to to zero

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

the long and confusing answer:

u have to think of your wallet as a tresor with a lot of little pile of coins inside

when u receive a transaction than a new little pile is put into ur tresor

this little pile have a coin-age of zero

when u send away coins than ur tresor take the youngest pile and remove the amount of coins u want to send

BUT the coin-age is set to zero for all coins in that little pile

thats the reason why people developed coin control so u can select from which little pilet u want to use the coins

the basic logic isnt optimal by automatic selecting the youngest pile because this could also be a pile with 10000 coins and age 7 days

but thats still lot more coin-age than a pile with 10 dmd age 30 days

ok basical i overanswered ur question sorry

our POS code try to counter the risc of losing coin-age by split big coin pile into smaller part when u successfull mint between 7-30 days coin-age

if u mint above 30 days coinage pile is not split but instead if u have multiple small pile they group together (up to 100 DMD) and increase the chance to recieve a POS reward

in one of the next wallet releases we will also add coin control maybe even in a advanced version (what other coins have now as coin control is very basic and required the user to choose the pile he wana use)

In short, no.


When coins are transferred from one address to another, the coinage for those coins resets.  Any accumulated coinage is lost.

Your coins started accumulating coinage when your transfer from Cryptsy to your wallet was confirmed.

A question about the pos..

I had lots of DMD in my wallet for months, a month ago I transferred them to cryptsy and then moved them back to my wallet.

Will I be able to get pos coins for the time BEFORE the transfer?

i think http://dmdpool.digsys.bg/ is victim of a DDoS attack

at least all signs looks like

very slow webfrontend

and insane slow block solving times

if ya have miners there switch solo mining or other pool until problem is solved

i expect a price drop first week because all old gathered up coin-age will be paid out
so i expect total coins will within a week jump from 450000 to ~600000

some might be silly and try to dump the POS earned coins

once this sell rush is over i expect a big rise of price

if i did wrong estimate and most coin holders stay holding their POS rewards too
(can happen because people who mint are not instaselling minners but investors who hold this kind of people wont sell fast at low price...)

which i strongly suggest to them because ur new generated coins will add to ur next 50% POS rewards
and holding most coins at least until POS reduced towards 25% (at 1500000 total coins) is in my eyes the plan to go

until then lot new stuff will be done for diamond and lot people will stay holding
because diamond did reach a spot between the big coins with longterm upwards trend
and beeing one of the crypto success stories people will talk about in 10 20 and 30 years

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

if u ask me why im pessimistic about how price shorttime develops
its maybe because i wana increase my share a bit and buy more cheap diamonds  
please sell drop the price as much as u can

(no premine coin so we from foundation have to take care on our own to get hands on some diamonds. the foundation share isnt given to us but used for the coin development and promotion)

The combination of POS and POW without reduced rewards will lead to more DMD in circulation (bad for price), the start of POS will make DMD more attractive (good for price). Not sure which of the two will influence price more though...

when there will be POS a Diamond will rise in price or will fall in price? and why?

Thank you for explaining this to me. Now I understand how this works (well, better at least )

POS is independent from mining
all that u need to earn POS rewards is coins that are old enough and a unlocked fully synced wallet to be able compete for the next POS block

with the wording simultanous active POW and POS we mean that like lot other coins we not set up in a way that POS only kicks in after POW stage ends

and with the 600 sec POS block time (should be better called block spacing) we archive that not many orphan blocks are created

and POW mining not interupted by chain-atempts to create POS rewards

for POS its not important to create regularly a block because our network is allways additional driven by endless POW

and once POS blocks are created they protect network for a long time (mature time 200 min)

i think our whole concept did take all experinces coins gathered since POS was imnvented and create the perfect Hybrid POW/POS setup

that why we called it Diamond Evolution

beside the unique total coins triggers (which i see at no other coin)
we mainly used existing technology but combined it in a perfect interacting way together
with main focus on wealth storage and growth
this way we not creating a generation 2 or generation 3 coin
but the top of generation 1 evolution

to be a generation 1 based coin is no shame
the most valueable coins are

Hello. I have a couple of (stupid?) questions. If PoS will be active simultaneously with PoW, do I have to run my wallet on a computer that already runs a miner? Or can I use any computer for minting?

I also see that on the OP it says "PoS block solving target time ~ 600 seconds" and "PoW block solving target time ~ 60 seconds". How can PoS then be active simultaneously with each PoW reward block? Or is it just a printing error?

Hope that someone can explain this, thanks.

pallas,

Nice work on porting Diamond to ARM. There are few things I would do differently, but it is basically ok. You are correct, qualifying random with boost is one thing done in the past, which I forgot to include in the latest code -- it is compiler specific -- some compilers bomb on it, other don't. There are also few other such places.

I don't believe you save any RAM by stripping the binary -- you only save disk space. Modern UNIX OS is page loading the code segments only, the symbols are in fact there to aid debugging only. But the ARM runtime might be different.

About the need to re-download block chain, could you send me the complete error so that we investigate why it is happening. You should also verify that your wallet is functioning properly by downloading the complete block chain from scratch. This is the ultimate test.

Can you prepare two text documents for inclusion in the Diamond code? Such as how to build on ARM and how to build on QNAP. Add your copyright there, and make sure it's compatible with the general Diamond copyright.

You also need to delete the old .bin file so a new one is generated. If you don't delete the .bin file, the miner will just use it (cached) and ignore you changed the source (the .cl file). It would recompile it only if you change mining parameters.

I expect dmd to rise once pos kicks in

make sure u wallet is unlock and pos is 7 days now 50 % beginning with total coins 450000 a 50% POS will be simultaneous active with the 1 DMD POW reward each block

Hello all - I have a basic staking/minting question.  When the POS kicks in do I manually have to do anything to stake/mint or does it happen automatically?  And then once it does stake/mint do I need to do something to make it happen again or is it also automatic every 30 days or so?  Is there any good reading material on how this whole thing works or can someone explain it please?

Thank you in advance.   

Thank you pallas for this detailed guide; donation has been sent.

BUILDING THE HEADLESS WALLET ON A QNAP ARM NAS
----------------------------------------------

CHANGES TO THE WALLET SOURCES:

- mkdir src/obj
- makefile.unix sets -msse2 flag that obviously doesn't work for arm

- makefile.unix: missing scrypt-arm.S (I got it from hobonickels github: download and put into src/)

   @@ -135,7 +135,8 @@ OBJS= \
     obj/pbkdf2.o \
     obj/scrypt_mine.o \
     obj/scrypt-x86.o \
-    obj/scrypt-x86_64.o
+    obj/scrypt-x86_64.o \
+    obj/scrypt-arm.o
 
 all: diamondd
@@ -158,6 +159,9 @@ obj/scrypt-x86.o: scrypt-x86.S
 obj/scrypt-x86_64.o: scrypt-x86_64.S
    $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<
 
+obj/scrypt-arm.o: scrypt-arm.S
+   $(CXX) -c $(xCXXFLAGS) -MMD -o $@ $<
+
 obj/%.o: %.cpp
    $(CXX) -c $(xCXXFLAGS) -MMD -MF $(@:%.o=%.d) -o $@ $<
    @cp $(@:%.o=%.d) $(@:%.o=%.P); \

- scrypt_mine.cpp: need to "else" instead of "elseif" or arm wouldn't get the declarations:

index afca59d..4fa1426 100644
--- a/src/scrypt_mine.cpp
+++ b/src/scrypt_mine.cpp
@@ -54,7 +54,8 @@ extern "C" void scrypt_core(uint32_t *X, uint32_t *V);
 extern "C" void scrypt_core_2way(uint32_t *X, uint32_t *Y, uint32_t *V);
 extern "C" void scrypt_core_3way(uint32_t *X, uint32_t *Y, uint32_t *Z, uint32_t *V);
 
-#elif defined(__i386__)
+#else

- main.cpp: ambiguous call to random(), need to specify it's the boost version:

index 1e40a7e..3a513e1 100644
--- a/src/main.cpp
+++ b/src/main.cpp
@@ -947,8 +947,8 @@ uint256 WantedByOrphan(const CBlock* pblockOrphan)
 
 int generateMTRandom(unsigned int s, int range)
 {
-    random::mt19937 gen(s);
-    random::uniform_int_distribution<> dist(1, range);
+    boost::random::mt19937 gen(s);
+    boost::random::uniform_int_distribution<> dist(1, range);
     return dist(gen);
 }

QNAP NAS specific:

- first of all install "ipkg" from the application center, open a terminal and install the build environment (TODO provide "ipkg install" command)
- don't compile into admin's home, it's too small: use another user or move to another directory
- for the same reason, don't do "make install", or do it but changing the prefix to /opt instead of /usr/local
- compile your own berkeleydb 4.8, boost library and, if you need it, miniupnpc too (see their documentation and read doc/build-unix.txt of any bitcoin-derived wallet)
- consider it may take a while: on my nas the boost library took a whole night to fully compile
- make with: CXXFLAGS='-DHAVE_CXX_STDHEADERS' BDB_INCLUDE_PATH='~/BerkeleyDB.4.8/include' BDB_LIB_PATH='~/BerkeleyDB.4.8/lib' \
   BOOST_INCLUDE_PATH='~/boost_1_55_0' BOOST_LIB_PATH='~/boost_1_55_0/stage/lib' make -f makefile.unix
- remember to run ldconfig on the two new lib paths and/or add to /etc/ld.so.conf
- because of some locale issue, "export LC_ALL=C" is needed before running the wallet
- strip debug info from the executable in order to save ram (we have little on a NAS): "strip diamondd"
- if you get "diamondd: kernel.cpp:412: unsigned int GetStakeModifierChecksum..." try downloading blockchain from OP.

Donations (DMD): dVrz69vZFrxJRH9AnKyHim7Hd3PhY3w9NQ

Let it shine let it shine

Sorry, its ok now, driven by vardiff. 

Oh, my bad, i havent realised its so simple Thanks a lot.

Got any hint for a good diff multiplier for 42mhs?