That multipool is bogus.
With 200gh 24h of mining BTC equal ~0.005 per day,
I mined 24hrs on the multipool and received 0.6364 BTCD which roughly makes 0.0014
Whats the deal with that, seems like some shortage on the payout
Topic: BTCD is no more - page 449. (Read 1328490 times)
Has anyone else not received a payout from http://BTCDPool.com yet?
I have had 149 mazacoin sitting there for a couple days...which has not been paid out in BTCD ( aprox. 50 -60 BTCD).
I have no way of contacting the pool operator as the pool does not provide contact info. ( NOTE: I prefer email, or even phone, instead of other tools that some pools use. Old fart here lol. )
I have had 149 mazacoin sitting there for a couple days...which has not been paid out in BTCD ( aprox. 50 -60 BTCD).
I have no way of contacting the pool operator as the pool does not provide contact info. ( NOTE: I prefer email, or even phone, instead of other tools that some pools use. Old fart here lol. )
no payout for me too!
did you succeed in contacting them ?
regards knauf1
hold my coins at 0.01 
I am holding and got 1.6 th mining in multipool..
hold my coins at 0.01
i wish i have BTCs to buy a lot more
Some good news for those of you frantically worried about the privacyServer knowing who you are communicating to.
I went through the code and realized that the privacyServer doesnt need to know the account of the sender. Of course it knows your IP address, but we already know how to use proxies to make the IP address pretty useless. Another way is to use a temporary acct that you create just for communicating to the privacyServer, and then when you send messages, you use your real account.
privacyServer sees traffic from a brand new temporary account with no history, it does see the destination, but if I bother to add a third onion layer, even this is pretty useless.
So, now you can not worry about your real account number being compromised by the privacyServer!
If there is anybody capable of reviewing C code, it would be nice to get an independent source code review to make sure I am not missing anything. PM me if you are interested. I want it to be someone arms length and presumably objective.
James
I went through the code and realized that the privacyServer doesnt need to know the account of the sender. Of course it knows your IP address, but we already know how to use proxies to make the IP address pretty useless. Another way is to use a temporary acct that you create just for communicating to the privacyServer, and then when you send messages, you use your real account.
privacyServer sees traffic from a brand new temporary account with no history, it does see the destination, but if I bother to add a third onion layer, even this is pretty useless.
So, now you can not worry about your real account number being compromised by the privacyServer!
If there is anybody capable of reviewing C code, it would be nice to get an independent source code review to make sure I am not missing anything. PM me if you are interested. I want it to be someone arms length and presumably objective.
James
Is there a big plan?
Naaa... the usual: Lots of big promises that never gets implemented at launch... followed by a pump and dump, and then we all move on to another coin...
When Satoshi issued his white paper, he took a year to release its implementation. His promises where available at launch, not in a "near" future.
You invest in something with potential
The potential hasn't changed... That is why I'm asking. Why are people investing even more as the price rises? There's no real determining factor?
I realize that this comes off as fud, and it sort of is. But I honestly want to know what makes these things tick to know what to look for in future investments. There was no new news, no new announcements, nothing changed as far as I can tell. Why did this explode?
maybe <1.2 million coins?
maybe ~100 coins per day
maybe released dev meeting log?
maybe people actually understand what I am building?
Or it could just be random chance?
So you don't expect a crash? Do you expect continuous growth?
So depending on your definition of "crash", maybe it does due to the volatility
We are talking about 1 million coins, probably only 400,000 that are actually being traded and $500,000 USD per day, so each BTCD is traded several times a day.
Anybody that says they can predict short term price under such whirlwind is lying.
Even my 85% accurate forex predictors wouldnt be able to get a very good accuracy for this sort of market.
Long term (measured in months), will BTCD be stuck at ~1 million marketcap?
Only if I fail to deliver the software
James
P.S. see my previous post
WTB 10000 BTCD @ .002
You invest in something with potential
The potential hasn't changed... That is why I'm asking. Why are people investing even more as the price rises? There's no real determining factor?
I realize that this comes off as fud, and it sort of is. But I honestly want to know what makes these things tick to know what to look for in future investments. There was no new news, no new announcements, nothing changed as far as I can tell. Why did this explode?
maybe <1.2 million coins?
maybe ~100 coins per day
maybe released dev meeting log?
maybe people actually understand what I am building?
Or it could just be random chance?
So you don't expect a crash? Do you expect continuous growth?
You invest in something with potential
The potential hasn't changed... That is why I'm asking. Why are people investing even more as the price rises? There's no real determining factor?
I realize that this comes off as fud, and it sort of is. But I honestly want to know what makes these things tick to know what to look for in future investments. There was no new news, no new announcements, nothing changed as far as I can tell. Why did this explode?
maybe <1.2 million coins?
maybe ~100 coins per day
maybe released dev meeting log?
maybe people actually understand what I am building?
Or it could just be random chance?
I just thought of a small leak of info
If I allow different length messages, then an attacker could deduce the type of message you are sending by tracking the size of the packets. Not sure how big of a problem this is. The problem with fixed sized messages is that it will waste a fair amount of bandwidth.
Ah, maybe this is one of the differences in privacy levels!
Yes, I like that. At lower levels of privacy, such small info leakage is accepted,but at higher levels of privacy, all messages will be of fixed size
James
If I allow different length messages, then an attacker could deduce the type of message you are sending by tracking the size of the packets. Not sure how big of a problem this is. The problem with fixed sized messages is that it will waste a fair amount of bandwidth.
Ah, maybe this is one of the differences in privacy levels!
Yes, I like that. At lower levels of privacy, such small info leakage is accepted,but at higher levels of privacy, all messages will be of fixed size
James
You could always add random length padding to your messages. However, this may be more trouble than it's worth for very small differences in size over fixed length.
this could help, but I cant easily calculate the leakage as it becomes quite complex
Do you have documentation somewhere on the types of messages and their format? I'd like to take a look.
[{"requestType":"processutx","NXT":"8989816935121514892","utx":"0201b93a3d01d00225c5fed2690701cf06f267e7c227b1a3c0dfa9c6fc3cdb593b3af6f16d65302 f8c71b555df3ec27c000000000000000000e1f50500000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000444a53bf9828e869e80300000000000031007b22617373657442223a2231363339323939383 439333238343339353338222c2271747942223a2231303030303030227d","sig":"2dec3f78c73a4181e8ac4417eff4036176313935f79667ea8c6bc88a4bfd438f","full":"c04e8b6d34244aa5aef98f095197e9b8d1c8a8a3c3d4e6774c3fc955fcaac6e9","time":1406084344},{"token":"d79fth95u83cu087m4js5pr7oqktvg537dctmf7sclmv3thq7ktbibpgp0f3ecg1uk4fnk98cml5uvf k1pqqe0em15c699vt1rs4admc3tugtv1jj59btt4rcj0e9pipkhqrs7m61mehd2krk9i819nvjlmhe0 tv"}]]
I keep adding new API calls daily. the first part of JSON is the actual API call, the second is a token that uses the first JSON object as the input. The processutx is one of the longer requests. There are currently over a dozen, probably another dozen more will be added this month. I just write them as I need them since they are easy enough to add.
James
P.S. I know, I should compress all the zeroes and I plan to use my jsoncodec once the API calls stabilize, just need a words list and should get nice 2 to 3x compression ratio
Don't sell under 500000 satoshi !!!
No you still have a chance , will go 0.0x for sure .
Is it me or this coin is *instant* mined in 14 days?
it was know since the beginning that there would be a short mining period. If you check out page one you'll see it in various articles through the recent media coverage.
Wow, price so high
You invest in something with potential
The potential hasn't changed... That is why I'm asking. Why are people investing even more as the price rises? There's no real determining factor?
I realize that this comes off as fud, and it sort of is. But I honestly want to know what makes these things tick to know what to look for in future investments. There was no new news, no new announcements, nothing changed as far as I can tell. Why did this explode?
there is a document & diagram, in the works to display the development process thus far, also if you take a look at jl777's previous post youll get an idea of the current status of anonymity development and additional features such as pNXT on github. its understandable that some of the technical information isnt quite clear but keep in mind the development has been daily.
I just thought of a small leak of info
If I allow different length messages, then an attacker could deduce the type of message you are sending by tracking the size of the packets. Not sure how big of a problem this is. The problem with fixed sized messages is that it will waste a fair amount of bandwidth.
Ah, maybe this is one of the differences in privacy levels!
Yes, I like that. At lower levels of privacy, such small info leakage is accepted,but at higher levels of privacy, all messages will be of fixed size
James
If I allow different length messages, then an attacker could deduce the type of message you are sending by tracking the size of the packets. Not sure how big of a problem this is. The problem with fixed sized messages is that it will waste a fair amount of bandwidth.
Ah, maybe this is one of the differences in privacy levels!
Yes, I like that. At lower levels of privacy, such small info leakage is accepted,but at higher levels of privacy, all messages will be of fixed size
James
You could always add random length padding to your messages. However, this may be more trouble than it's worth for very small differences in size over fixed length.
this could help, but I cant easily calculate the leakage as it becomes quite complex
Do you have documentation somewhere on the types of messages and their format? I'd like to take a look.
BitcoinDark by xpool - The Official BTCD Multipool
PROP reward system
BTCD Payouts
Scrypt & SHA256 & X11 Algo's
DDoS Protected
High Performance Backend
Simple setup and usage
1% Fee
To mine:
How does it work?
xpool offers 3 different sets of coins to mine. SHA256, Scrypt and X11. Each algorithm runs on a shift (see below). The confirmed coins are traded throughout the duration of the shift automatically to maximize the profits from exchanging them into BTCD. Once the shift ends, the shift is moved into "Confirming" status while all the coins are confirmed as successfully traded and exchanged, the BTCD payments are sent.
Current shifts run 24 hours, Monday - Friday and end at 7PM Eastern each day except Saturday & Sunday. The weekend shift ends on the Monday. Payments are then finialized and typically complete 2-3 hours after a shift ends.
The advantage of the pool is that you can utilize your any GPU, CPU and older ASIC equipment to earn you the more desired BitcoinDark.
xpool offers 3 different sets of coins to mine. SHA256, Scrypt and X11. Each algorithm runs on a shift (see below). The confirmed coins are traded throughout the duration of the shift automatically to maximize the profits from exchanging them into BTCD. Once the shift ends, the shift is moved into "Confirming" status while all the coins are confirmed as successfully traded and exchanged, the BTCD payments are sent.
Current shifts run 24 hours, Monday - Friday and end at 7PM Eastern each day except Saturday & Sunday. The weekend shift ends on the Monday. Payments are then finialized and typically complete 2-3 hours after a shift ends.
The advantage of the pool is that you can utilize your any GPU, CPU and older ASIC equipment to earn you the more desired BitcoinDark.
Cheers and Happy Hashing!
Donations welcome or tip me, crackers, on IRC!
Any issues, please report them here or feel free to PM me, as I can't always see every post.
Donations welcome or tip me, crackers, on IRC!
Any issues, please report them here or feel free to PM me, as I can't always see every post.
Today's shift payments have finished. Over 295 BTCD sent out to miners on all 3 algos! The x11 stats per miner got corrupted but ya'll x11'ers got your BTCD!
Is it me or this coin is *instant* mined in 14 days?
Jump to: