[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 4751.

xsoft

newbie

Activity: 60

Merit: 0

Im still unable to compile https://github.com/ig0tik3d/darkcoin-cpuminer-1.2c

Yeah, I know that BAMT suc*s and that gcc compiler could be old.
But Ive trying to make this work for 3hours and nothing (several linux machines, vps, ...). I have cpuminer but withou X11 support.

Please, can somebody upload compiled version? (non-AES version)
Thanks.

Code:

/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c# make
make all-recursive
make[1]: Entering directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c'
Making all in compat
make[2]: Entering directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c/compat'
Making all in jansson
make[3]: Entering directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c/compat/jansson'
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -O3 -msse2 -MT dump.o -MD -MP -MF .deps/dump.Tpo -c -o dump.o dump.c
mv -f .deps/dump.Tpo .deps/dump.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -O3 -msse2 -MT hashtable.o -MD -MP -MF .deps/hashtable.Tpo -c -o hashtable.o hashtable.c
mv -f .deps/hashtable.Tpo .deps/hashtable.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -O3 -msse2 -MT load.o -MD -MP -MF .deps/load.Tpo -c -o load.o load.c
mv -f .deps/load.Tpo .deps/load.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -O3 -msse2 -MT strbuffer.o -MD -MP -MF .deps/strbuffer.Tpo -c -o strbuffer.o strbuffer.c
mv -f .deps/strbuffer.Tpo .deps/strbuffer.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -O3 -msse2 -MT utf.o -MD -MP -MF .deps/utf.Tpo -c -o utf.o utf.c
mv -f .deps/utf.Tpo .deps/utf.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -O3 -msse2 -MT value.o -MD -MP -MF .deps/value.Tpo -c -o value.o value.c
mv -f .deps/value.Tpo .deps/value.Po
rm -f libjansson.a
ar cru libjansson.a dump.o hashtable.o load.o strbuffer.o utf.o value.o
ranlib libjansson.a
make[3]: Leaving directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c/compat/jansson'
make[3]: Entering directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c/compat'
make[2]: Leaving directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c/compat'
make[2]: Entering directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c'
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-cpu-miner.o -MD -MP -MF .deps/minerd-cpu-miner.Tpo -c -o minerd-cpu-miner.o `test -f 'cpu-miner.c' || echo './'`cpu-miner.c
cpu-miner.c:179:44: warning: backslash and newline separated by space
cpu-miner.c: In function ‘main’:
cpu-miner.c:1328: warning: implicit declaration of function ‘init_Xhash_contexts’
mv -f .deps/minerd-cpu-miner.Tpo .deps/minerd-cpu-miner.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-util.o -MD -MP -MF .deps/minerd-util.Tpo -c -o minerd-util.o `test -f 'util.c' || echo './'`util.c
mv -f .deps/minerd-util.Tpo .deps/minerd-util.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-sha2.o -MD -MP -MF .deps/minerd-sha2.Tpo -c -o minerd-sha2.o `test -f 'x2/sha2.c' || echo './'`x2/sha2.c
mv -f .deps/minerd-sha2.Tpo .deps/minerd-sha2.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-sha2-arm.o -MD -MP -MF .deps/minerd-sha2-arm.Tpo -c -o minerd-sha2-arm.o `test -f 'x2/sha2-arm.S' || echo './'`x2/sha2-arm.S
mv -f .deps/minerd-sha2-arm.Tpo .deps/minerd-sha2-arm.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-sha2-x86.o -MD -MP -MF .deps/minerd-sha2-x86.Tpo -c -o minerd-sha2-x86.o `test -f 'x2/sha2-x86.S' || echo './'`x2/sha2-x86.S
mv -f .deps/minerd-sha2-x86.Tpo .deps/minerd-sha2-x86.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-sha2-x64.o -MD -MP -MF .deps/minerd-sha2-x64.Tpo -c -o minerd-sha2-x64.o `test -f 'x2/sha2-x64.S' || echo './'`x2/sha2-x64.S
mv -f .deps/minerd-sha2-x64.Tpo .deps/minerd-sha2-x64.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-scrypt.o -MD -MP -MF .deps/minerd-scrypt.Tpo -c -o minerd-scrypt.o `test -f 'x2/scrypt.c' || echo './'`x2/scrypt.c
mv -f .deps/minerd-scrypt.Tpo .deps/minerd-scrypt.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-scrypt-arm.o -MD -MP -MF .deps/minerd-scrypt-arm.Tpo -c -o minerd-scrypt-arm.o `test -f 'x2/scrypt-arm.S' || echo './'`x2/scrypt-arm.S
mv -f .deps/minerd-scrypt-arm.Tpo .deps/minerd-scrypt-arm.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-scrypt-x86.o -MD -MP -MF .deps/minerd-scrypt-x86.Tpo -c -o minerd-scrypt-x86.o `test -f 'x2/scrypt-x86.S' || echo './'`x2/scrypt-x86.S
mv -f .deps/minerd-scrypt-x86.Tpo .deps/minerd-scrypt-x86.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-scrypt-x64.o -MD -MP -MF .deps/minerd-scrypt-x64.Tpo -c -o minerd-scrypt-x64.o `test -f 'x2/scrypt-x64.S' || echo './'`x2/scrypt-x64.S
mv -f .deps/minerd-scrypt-x64.Tpo .deps/minerd-scrypt-x64.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-aes_helper.o -MD -MP -MF .deps/minerd-aes_helper.Tpo -c -o minerd-aes_helper.o `test -f 'x5/aes_helper.c' || echo './'`x5/aes_helper.c
mv -f .deps/minerd-aes_helper.Tpo .deps/minerd-aes_helper.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-luffa_for_sse2.o -MD -MP -MF .deps/minerd-luffa_for_sse2.Tpo -c -o minerd-luffa_for_sse2.o `test -f 'x5/luffa_for_sse2.c' || echo './'`x5/luffa_for_sse2.c
mv -f .deps/minerd-luffa_for_sse2.Tpo .deps/minerd-luffa_for_sse2.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-shavite.o -MD -MP -MF .deps/minerd-shavite.Tpo -c -o minerd-shavite.o `test -f 'x5/shavite.c' || echo './'`x5/shavite.c
mv -f .deps/minerd-shavite.Tpo .deps/minerd-shavite.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-cubehash_sse2.o -MD -MP -MF .deps/minerd-cubehash_sse2.Tpo -c -o minerd-cubehash_sse2.o `test -f 'x5/cubehash_sse2.c' || echo './'`x5/cubehash_sse2.c
mv -f .deps/minerd-cubehash_sse2.Tpo .deps/minerd-cubehash_sse2.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-nist.o -MD -MP -MF .deps/minerd-nist.Tpo -c -o minerd-nist.o `test -f 'x5/vect128/nist.c' || echo './'`x5/vect128/nist.c
mv -f .deps/minerd-nist.Tpo .deps/minerd-nist.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-vector.o -MD -MP -MF .deps/minerd-vector.Tpo -c -o minerd-vector.o `test -f 'x5/vect128/vector.c' || echo './'`x5/vect128/vector.c
x5/vect128/vector.c:71:1: warning: "X" redefined
x5/vect128/vector.c:66:1: warning: this is the location of the previous definition
x5/vect128/vector.c:794:1: warning: "STEP_1" redefined
x5/vect128/vector.c:540:1: warning: this is the location of the previous definition
x5/vect128/vector.c:803:1: warning: "STEP_2" redefined
x5/vect128/vector.c:564:1: warning: this is the location of the previous definition
x5/vect128/vector.c:806:1: warning: "STEP" redefined
x5/vect128/vector.c:569:1: warning: this is the location of the previous definition
x5/vect128/vector.c:827:1: warning: "ROUND" redefined
x5/vect128/vector.c:577:1: warning: this is the location of the previous definition
x5/vect128/vector.c:852:1: warning: "PERM_START" redefined
x5/vect128/vector.c:850:1: warning: this is the location of the previous definition
x5/vect128/vector.c:854:1: warning: "PERM_START" redefined
x5/vect128/vector.c:852:1: warning: this is the location of the previous definition
x5/vect128/vector.c:856:1: warning: "PERM_START" redefined
x5/vect128/vector.c:854:1: warning: this is the location of the previous definition
x5/vect128/vector.c:862:1: warning: "PERM_START" redefined
x5/vect128/vector.c:856:1: warning: this is the location of the previous definition
x5/vect128/vector.c:864:1: warning: "PERM_START" redefined
x5/vect128/vector.c:862:1: warning: this is the location of the previous definition
x5/vect128/vector.c:866:1: warning: "PERM_START" redefined
x5/vect128/vector.c:864:1: warning: this is the location of the previous definition
x5/vect128/vector.c:868:1: warning: "PERM_START" redefined
x5/vect128/vector.c:866:1: warning: this is the location of the previous definition
x5/vect128/vector.c:875:1: warning: "PERM_START" redefined
x5/vect128/vector.c:868:1: warning: this is the location of the previous definition
mv -f .deps/minerd-vector.Tpo .deps/minerd-vector.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-echo.o -MD -MP -MF .deps/minerd-echo.Tpo -c -o minerd-echo.o `test -f 'x5/echo.c' || echo './'`x5/echo.c
mv -f .deps/minerd-echo.Tpo .deps/minerd-echo.Po
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -I./compat/jansson -O3 -msse2 -MT minerd-xcoin.o -MD -MP -MF .deps/minerd-xcoin.Tpo -c -o minerd-xcoin.o `test -f 'xcoin.c' || echo './'`xcoin.c
In file included from xcoin.c:25:
x6/jh_sse2_opt64.h:32: error: redefinition of typedef ‘BitSequence’
x5/defs_x5.h:5: note: previous declaration of ‘BitSequence’ was here
x6/jh_sse2_opt64.h:33: error: redefinition of typedef ‘DataLength’
x5/defs_x5.h:6: note: previous declaration of ‘DataLength’ was here
xcoin.c: In function ‘Xhash’:
xcoin.c:97: warning: assignment discards qualifiers from pointer target type
xcoin.c:112: warning: right shift count >= width of type
xcoin.c:112: warning: right shift count >= width of type
xcoin.c:112: warning: right shift count >= width of type
xcoin.c:112: warning: right shift count >= width of type
make[2]: *** [minerd-xcoin.o] Error 1
make[2]: Leaving directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/miners.test/cpu5/darkcoin-cpuminer-1.2c'
make: *** [all] Error 2

Lauda

legendary

Activity: 2674

Merit: 3000

Terminated.

Quote from: toknormal on July 15, 2014, 09:33:20 AM

All those waiting to "buy back in" when the next development is announced, your numbers are mounting. You know what that means - liquidity crisis.

Even with the current price sink there's only about 10,000 DRK on the orderbook. When all these "I'll buy back when the price hits x" or "...when RC4 is announced" folk decide to go long they're going to be fighting over vapour because there's barely any volume in the current dip and so the volume in the asks will dry up like a puddle of meths on a car bonnet in death valley.

The trades right now are all in single or double figures. 1, 2, 10 and 20 DRK shots. The market is illiquid. I'm sorry, but you can't buy in at 8 or 7 or 6. Look what happened last night as soon as any significant liquidity appeared (around 1.5k) - munched in a few minutes.

In short, it's not price you people should be worrying about, it's liquidity. And right now there isn't any cos nobody's selling.

Exactly. If you consider in the amount of those people that will also then setup a MN, in addition to the already increasing number, the fight shall be a hard one.

crackfoo

legendary

Activity: 3570

Merit: 1126

Quote from: AngusCanine on July 15, 2014, 10:04:00 AM

Quote from: crackfoo on July 14, 2014, 10:57:02 PM

Quote from: Ignition75 on July 14, 2014, 10:45:44 PM

Quote from: AngusCanine on July 14, 2014, 09:29:36 PM

Any opions on xpool.ca . Are they fair with their share distribution my s1 says my best share was 1,679,761,040 but my share count was only 6,500,000 for the shift?

I tried it for 3 or 4 days, I was getting about half the DRK I would be getting if I was mining DRK directly... Then as soon as I left they had a bumper run with URO and I missed out on a decent payout...

So my advice would be, give it a week before coming to any conclusions...

Our SHA shift just paid out it's largest payment yet (21.2723 DRK), 2x the payout as last shift due to some hot coins on SHA256 right now. They're still hot to so next shift will likely be a good one too but only if more SHA256 miners hop on.

Cheers!

sorry I'm unfamiliar with how payouts work, my s1 shows best share. If my best share is larger than than total shares paid for shift what happens there ? Is the shares on the pool different the the shares my s1 recognizes?

Only confirmed shares are paid. Confirmed shares, are shares that you've submitted and contributed to the finding of a block and that has matured during the shift.

illodin

hero member

Activity: 966

Merit: 1003

Quote from: luigi1111 on July 15, 2014, 10:11:42 AM

The "trustless" systems thus described (like multisig) have their own issues. What happens if someone dies? I think there is a "two out of three" or similar setup that could help with that, but it's still not perfect (particularly if one of the people involved has more coins at stake than the rest; the two with less could collude and take the coins from the guy with more, etc).

Interested to hear more ideas though. (also considering offering my own services, but yeah, always that trust thing) Edit: or just use crouton's.

There could be a smart contract created that expires in 30 days (or whatever duration you choose to run the MN), and after 30 days it sends the coins back. No idea how to do that though, probably something that could be done with BitHalo / BlackHalo.

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: luigi1111 on July 15, 2014, 10:11:42 AM

Quote from: libivan on July 15, 2014, 09:55:53 AM

Quote from: thelonecrouton on July 15, 2014, 09:46:28 AM

There are 7, possibly 8 100DRK Masternode shares awaiting fulfillment here:

https://darkcointalk.org/threads/new-masternode-share-9-partners-wanted-100drk-each-1-month-renewable-agreement.1785/

I charge NO FEES (just your share of server costs) and can exchange real-world contact details if required.

with this kind of problem I wouldn't trust ANYONE, unless there's any trustless mechanism available (e.g. http://www.reddit.com/r/DRKCoin/comments/2aopdl/trustless_coin_leasing_system_that_would_allow )

Quote from: illodin on July 15, 2014, 09:48:02 AM

Is it clear that DZ is a scammer and not just dead or in hospital or something?

the thing is, even his long time "partner" is giving lame excuses now...

it's a bad image for the whole darkcoin community. that's the reason why people want government regulations for cryptocurrencies... the scammers Sad

The "trustless" systems thus described (like multisig) have their own issues. What happens if someone dies? I think there is a "two out of three" or similar setup that could help with that, but it's still not perfect (particularly if one of the people involved has more coins at stake than the rest; the two with less could collude and take the coins from the guy with more, etc).

Interested to hear more ideas though. (also considering offering my own services, but yeah, always that trust thing) Edit: or just use crouton's.

I agree, multisig introduces as many problems as it solves. At the end of the day if you are doing business with someone you ideally need to know your partners well. There is no cryptographic wizardry that eliminates the possibility of someone deciding to act like an ass.

edit, WRT illodin's post below: smart contracts cetainly shift the trust elsewhere (eg. into software) but they don't eliminate it. Nothing is without risk and you still need to do your due diligence.

illodin

hero member

Activity: 966

Merit: 1003

Quote from: thelonecrouton on July 15, 2014, 10:06:45 AM

Not seeing an issue here for Darkcoin.

That's right, as I understand it the issue is with "unlinkable" transactions like CryptoNote.

salmion

hero member

Activity: 560

Merit: 500

Quote from: AngusCanine on July 15, 2014, 10:04:00 AM

Quote from: crackfoo on July 14, 2014, 10:57:02 PM

Quote from: Ignition75 on July 14, 2014, 10:45:44 PM

Quote from: AngusCanine on July 14, 2014, 09:29:36 PM

Any opions on xpool.ca . Are they fair with their share distribution my s1 says my best share was 1,679,761,040 but my share count was only 6,500,000 for the shift?

I tried it for 3 or 4 days, I was getting about half the DRK I would be getting if I was mining DRK directly... Then as soon as I left they had a bumper run with URO and I missed out on a decent payout...

So my advice would be, give it a week before coming to any conclusions...

Our SHA shift just paid out it's largest payment yet (21.2723 DRK), 2x the payout as last shift due to some hot coins on SHA256 right now. They're still hot to so next shift will likely be a good one too but only if more SHA256 miners hop on.

Cheers!

sorry I'm unfamiliar with how payouts work, my s1 shows best share. If my best share is larger than than total shares paid for shift what happens there ? Is the shares on the pool different the the shares my s1 recognizes?

Best share is different to shares on a pool.

Quote from: odolvlobo on October 20, 2013, 01:58:10 PM

Quote from: timk225 on October 18, 2013, 01:49:22 PM

In the CGMiner display, it'll show the current coin difficulty (67.6 Million is how it shows LTC right now, although you divide that by 65536 to get the actual difficulty of 1031 at this moment).
And under Best Share, it says my best is 5.23 Million.
So what does that mean? The best hash one of my GPUs on that PC made was roughly 1/12 of a complete valid hash? What if my Best Share was 1 million or 10 million? Would one of my hashes be closer to a correct answer if a higher number is showing in Best Share?

The Best Share shows the difficulty value corresponding to the lowest hash value that your miner has computed so far.

The concept is simple, but it is difficult to explain. The difficulty determines the highest hash value that can solve a block. If your miner computes a hash value that is lower than that maximum, then you have solved a block.

Keep in mind that there is some ambiguity in the term "difficulty". Generally, when people refer to the difficulty, they are referring to the value that determines the maximum hash value that will solve a block. However, when someone refers to the difficulty of a particular block, they really mean the difficulty value that corresponds to the block's hash value . In other words, if a block's difficulty is X, then it has a hash value that would have solved the block the difficulty were X. A block doesn't really have a difficulty, but sometimes it is useful to refer to the hash value in terms of difficulty.

If your Best Share is more than the current difficulty, it means that you have solved at least one block.
If your Best Share is more than the current share difficulty, it means that you have gotten at least one share.

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: ibcrypto on July 15, 2014, 10:08:12 AM

Wallet App on this rig would do DRK right...

https://www.blackphone.ch/

Sounds like you can install Google Play, or just use discrete apks.

https://support.blackphone.ch/customer/portal/questions/8035103-can-i-use-normal-apps-from-the-android-store-

So you should be able to use the existing android wallet.

raganius

sr. member

Activity: 308

Merit: 250

Quote from: ddink7 on July 15, 2014, 09:58:03 AM

Quote from: illodin on July 15, 2014, 09:48:02 AM

Is it clear that DZ is a scammer and not just dead or in hospital or something?

FWIW, I sent DZ 750 DRK and then decided to increase my DRK holdings and set up my own masternode myself. I requested a refund of the 750 DRK stake and received it within 48 hours. Maybe I was just lucky, I don't know. Just feel like I should post that here.

Yes, ddink7 is right. It's early to make assumptions: It would make no sense that DZ acted dishonestly, he had a lot to earn as MasterNode admin, and he has shared so much of his personal info.

I am sure something unexpected happened to DZ and everything will be fine in the end.

luigi1111

legendary

Activity: 1105

Merit: 1000

Quote from: libivan on July 15, 2014, 09:55:53 AM

Quote from: thelonecrouton on July 15, 2014, 09:46:28 AM

There are 7, possibly 8 100DRK Masternode shares awaiting fulfillment here:

https://darkcointalk.org/threads/new-masternode-share-9-partners-wanted-100drk-each-1-month-renewable-agreement.1785/

I charge NO FEES (just your share of server costs) and can exchange real-world contact details if required.

with this kind of problem I wouldn't trust ANYONE, unless there's any trustless mechanism available (e.g. http://www.reddit.com/r/DRKCoin/comments/2aopdl/trustless_coin_leasing_system_that_would_allow )

Quote from: illodin on July 15, 2014, 09:48:02 AM

Is it clear that DZ is a scammer and not just dead or in hospital or something?

the thing is, even his long time "partner" is giving lame excuses now...

it's a bad image for the whole darkcoin community. that's the reason why people want government regulations for cryptocurrencies... the scammers Sad

The "trustless" systems thus described (like multisig) have their own issues. What happens if someone dies? I think there is a "two out of three" or similar setup that could help with that, but it's still not perfect (particularly if one of the people involved has more coins at stake than the rest; the two with less could collude and take the coins from the guy with more, etc).

Interested to hear more ideas though. (also considering offering my own services, but yeah, always that trust thing) Edit: or just use crouton's.

ibcrypto

jr. member

Activity: 61

Merit: 1

Wallet App on this rig would do DRK right...

https://www.blackphone.ch/

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: illodin on July 15, 2014, 10:02:37 AM

AnonyMint's at it again:

Quote from: AnonyMint on July 15, 2014, 09:52:08 AM

This is very preliminary, but it appears to me that all anonymous coins based on unlinkability will not be able to solve the very serious double-spend threat.

If am correct, this is both a major and fundamental solution for longest chain rule of proof-of-work, but it also eliminates unlinkability as a anonymity solution.

Sorry to say. Again this is preliminary, and needs more peer review.

Quote from: AnonyMint on July 15, 2014, 09:32:18 AM

My proposal is that you don't trust the longest chain until considerable n confirmations have transpired, because the majority will be trying to unwind those bogus double-spends. So in my proposal, not only do you not deliver goods until a payment has n (usually 1 - 6) confirmations, but also you don't accept payment from a transaction (history) unless the prior transaction has much more than n (say 100 or so) confirmations. Abstractly the smoothing filter applies from both directions.

Note that CryptoNote ring signatures (and probably Zerocash and Zerocoin also) breaks the type of unwinding in my proposal because derivative transactions are unlinkable.

So, wait until the network has confirmed the transaction a number of times then... like everyone already does.

Not seeing an issue here for Darkcoin.

AngusCanine

legendary

Activity: 1414

Merit: 1001

To weird to live To rare to die

Quote from: crackfoo on July 14, 2014, 10:57:02 PM

Quote from: Ignition75 on July 14, 2014, 10:45:44 PM

Quote from: AngusCanine on July 14, 2014, 09:29:36 PM

Any opions on xpool.ca . Are they fair with their share distribution my s1 says my best share was 1,679,761,040 but my share count was only 6,500,000 for the shift?

I tried it for 3 or 4 days, I was getting about half the DRK I would be getting if I was mining DRK directly... Then as soon as I left they had a bumper run with URO and I missed out on a decent payout...

So my advice would be, give it a week before coming to any conclusions...

Our SHA shift just paid out it's largest payment yet (21.2723 DRK), 2x the payout as last shift due to some hot coins on SHA256 right now. They're still hot to so next shift will likely be a good one too but only if more SHA256 miners hop on.

Cheers!

sorry I'm unfamiliar with how payouts work, my s1 shows best share. If my best share is larger than than total shares paid for shift what happens there ? Is the shares on the pool different the the shares my s1 recognizes?

illodin

hero member

Activity: 966

Merit: 1003

AnonyMint's at it again:

Quote from: AnonyMint on July 15, 2014, 09:52:08 AM

This is very preliminary, but it appears to me that all anonymous coins based on unlinkability will not be able to solve the very serious double-spend threat.

If am correct, this is both a major and fundamental solution for longest chain rule of proof-of-work, but it also eliminates unlinkability as a anonymity solution.

Sorry to say. Again this is preliminary, and needs more peer review.

Quote from: AnonyMint on July 15, 2014, 09:32:18 AM

My proposal is that you don't trust the longest chain until considerable n confirmations have transpired, because the majority will be trying to unwind those bogus double-spends. So in my proposal, not only do you not deliver goods until a payment has n (usually 1 - 6) confirmations, but also you don't accept payment from a transaction (history) unless the prior transaction has much more than n (say 100 or so) confirmations. Abstractly the smoothing filter applies from both directions.

Note that CryptoNote ring signatures (and probably Zerocash and Zerocoin also) breaks the type of unwinding in my proposal because derivative transactions are unlinkable.

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: libivan on July 15, 2014, 09:55:53 AM

Quote from: thelonecrouton on July 15, 2014, 09:46:28 AM

There are 7, possibly 8 100DRK Masternode shares awaiting fulfillment here:

https://darkcointalk.org/threads/new-masternode-share-9-partners-wanted-100drk-each-1-month-renewable-agreement.1785/

I charge NO FEES (just your share of server costs) and can exchange real-world contact details if required.

with this kind of problem I wouldn't trust ANYONE, unless there's any trustless mechanism available (e.g. http://www.reddit.com/r/DRKCoin/comments/2aopdl/trustless_coin_leasing_system_that_would_allow )

Quote from: illodin on July 15, 2014, 09:48:02 AM

Is it clear that DZ is a scammer and not just dead or in hospital or something?

the thing is, even his long time "partner" is giving lame excuses now...

it's a bad image for the whole darkcoin community. that's the reason why people want government regulations for cryptocurrencies... the scammers Sad

What exactly has government regulation done to protect people from the illegal machinations of banks and the rest of the financial sector? You should have a word with some Cypriots about government regulation...

If you are in the EU, laws have already been passed that state clearly that when you deposit money in a bank, it no longer belongs to you.

Regulation is a joke at the expense of the taxpayer, it exists to protect big business, not to protect the little people.

ddink7

legendary

Activity: 1120

Merit: 1000

Quote from: illodin on July 15, 2014, 09:48:02 AM

Is it clear that DZ is a scammer and not just dead or in hospital or something?

FWIW, I sent DZ 750 DRK and then decided to increase my DRK holdings and set up my own masternode myself. I requested a refund of the 750 DRK stake and received it within 48 hours. Maybe I was just lucky, I don't know. Just feel like I should post that here.

libivan

full member

Activity: 210

Merit: 100

Quote from: thelonecrouton on July 15, 2014, 09:46:28 AM

There are 7, possibly 8 100DRK Masternode shares awaiting fulfillment here:

https://darkcointalk.org/threads/new-masternode-share-9-partners-wanted-100drk-each-1-month-renewable-agreement.1785/

I charge NO FEES (just your share of server costs) and can exchange real-world contact details if required.

with this kind of problem I wouldn't trust ANYONE, unless there's any trustless mechanism available (e.g. http://www.reddit.com/r/DRKCoin/comments/2aopdl/trustless_coin_leasing_system_that_would_allow )

Quote from: illodin on July 15, 2014, 09:48:02 AM

Is it clear that DZ is a scammer and not just dead or in hospital or something?

the thing is, even his long time "partner" is giving lame excuses now...

it's a bad image for the whole darkcoin community. that's the reason why people want government regulations for cryptocurrencies... the scammers Sad

Propulsion

hero member

Activity: 658

Merit: 500

The Buck Stops Here.

Quote from: CripLib on July 15, 2014, 09:41:08 AM

Update on the DyslexicZombei's Darkcoin MasterNode Services problem, as it is of interest to the whole Darkcoin Community:

Thank you for your support.

Lib

Quote from: CripLib on July 15, 2014, 09:28:25 AM

UPDATE:

I have just received a reply from DZ's partner as follows:

Quote from: thomas_s on July 15, 2014, 02:20:41 PM

Hi CripLib,

I was never fully brought on board for the darkcoin masternodes and don't actively participate in it / have never, while I was planning on it I was never contacted with what I needed to do.

--Thomas

My reply:

Quote from: CripLib on July 15, 2014, 02:26:50 PM

Quote from: thomas_s on July 15, 2014, 02:20:41 PM

Hi CripLib,

I was never fully brought on board for the darkcoin masternodes and don't actively participate in it / have never, while I was planning on it I was never contacted with what I needed to do.

--Thomas

Thank you, Thomas, for your reply. I am so sorry that it took so long for you to clarify it. I'll let the community know it.

Can you please help us get in touch with DZ, or at least understand what is going on with him. as he has been your partner for such a long time, as it seems, it is natural that you are possible to help as here.

Thnak you.

What we can do now:

- We must be clear as who here wants to ACT for a solution, and we must form a group;
- This group must contact the forum admins and request them disclose DZ's IPs information in order that he is tracked down;
- With the knowledge of DZ's real location, start the criminal procedures needed according to his Jurisdiction;
- If he is in the United States, for example, the possible scam victims should take this whole thread to be printed certified as a document in any local (English speaking) Notarial Service or in any United States Consulate, in order to keep the evidences protected.

Let's exchange PMs. let's act.

Just wanted to post this here really quick. DarkcoinTalk will never share a users IP address.

If you have been scammed/stolen, it is your responsibility to remedy the situation.

Sorry.

P.S. I also think your jumping to conclusions way too fast.

illodin

hero member

Activity: 966

Merit: 1003

Is it clear that DZ is a scammer and not just dead or in hospital or something?

thelonecrouton

legendary

Activity: 966

Merit: 1000

Quote from: CripLib on July 15, 2014, 09:41:08 AM

Update on the DyslexicZombei's Darkcoin MasterNode Services problem, as it is of interest to the whole Darkcoin Community:

Thank you for your support.

Lib

Quote from: CripLib on July 15, 2014, 09:28:25 AM

UPDATE:

I have just received a reply from DZ's partner as follows:

Quote from: thomas_s on July 15, 2014, 02:20:41 PM

Hi CripLib,

I was never fully brought on board for the darkcoin masternodes and don't actively participate in it / have never, while I was planning on it I was never contacted with what I needed to do.

--Thomas

My reply:

Quote from: CripLib on July 15, 2014, 02:26:50 PM

Quote from: thomas_s on July 15, 2014, 02:20:41 PM

Hi CripLib,

I was never fully brought on board for the darkcoin masternodes and don't actively participate in it / have never, while I was planning on it I was never contacted with what I needed to do.

--Thomas

Thank you, Thomas, for your reply. I am so sorry that it took so long for you to clarify it. I'll let the community know it.

Can you please help us get in touch with DZ, or at least understand what is going on with him. as he has been your partner for such a long time, as it seems, it is natural that you are possible to help as here.

Thnak you.

What we can do now:

- We must be clear as who here wants to ACT for a solution, and we must form a group;
- This group must contact the forum admins and request them disclose DZ's IPs information in order that he is tracked down;
- With the knowledge of DZ's real location, start the criminal procedures needed according to his Jurisdiction;
- If he is in the United States, for example, the possible scam victims should take this whole thread to be printed certified as a document in any local (English speaking) Notarial Service or in any United States Consulate, in order to keep the evidences protected.

Let's exchange PMs. let's act.

There are 7, possibly 8 100DRK Masternode shares awaiting fulfillment here:

https://darkcointalk.org/threads/new-masternode-share-9-partners-wanted-100drk-each-1-month-renewable-agreement.1785/

I charge NO FEES (just your share of server costs) and can exchange real-world contact details if required.

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 4751. (Read 9723814 times)