Topic: BTCD is no more - page 425. (Read 1328490 times)

I think I may have found the issue if this help you out under the X11 protocol in the statistics under the x11 protocol which I'm mining at there are 0 confirms across the board and very few pending blocks(1). Is it possible everyone on X11 over the weekend bailed so now it's totally pointless mining with x11? Or it could mean that the x11 multipool is having problems. Screeny:

I HAVE read the details and have received a small payout(1/3rd of a days worth) for the weekend, AFTER the payout I still have 810070 shares unconfirmed, still after now 6+ hours after the Monday payout for the weekend. Are those shares lost? Will they be confirmed by Tuesday night? I received the equivalent of about a 1/3 of a day of mining after the weekend, which I'm assuming is the former unconfirmed leftovers from Friday. After 3 days of mining I shouldn't receive only a 1/3 of a days worth. On other pools I've been on the blocks are confirmed as they mature and even if the payout is only once a day those shares are confirmed. Payout date should not affect the maturing of the blocks. As of a few hours ago, I turned my miners to the pool again as a test and the unconfirmed keep going up but no confirms yet after 3+ hours which is not the behaviour of the site last week. So I ask what changed? Why do I have 3 days worth of shares still unconfirmed after and I quote from your site "The weekend shift ends on the Monday. Payments are then finialized and typically complete 2-3 hours after a shift ends. When a shift ends all the coins that were found and matured will have been exchanged and converted into BTCD" does that statement not say that after the weekend all the shares you've mined (810070) will be confirmed and paid out on Monday night? Again, why do I have 3 days of mining stuck in "unconfirmed"? Why after hours later my test mining just keeps the unconfirmed going up with zero confirms? That wasn't the behavior of the site last week. Maybe look into my account if you don't mind you don't have an email on the site so heres my wallet. Thanks.

wallet address:

RBSR6mbcCwvJVNyKEgk5X2Qn4g64Y8KdVm


Maybe it's a display issue(probably not according to the payout) but my payout for the entire weekend was only .14 of a BTCD when it's usually .39 a day. As you can see from the below screenshot out of the whole weekend I only got 125000 shares confirmed for a payout. Strange no? Don't get me wrong I love your pool but something is amiss. I'll throw my miners back on it and see what happens tomorrow morning.

P.S. A nice big email icon on the pool would eliminate these posts. It's probably more useful that your chat icon which I've never seen anyone on and yes I tried that first. This was the last resort.

Screeny:

Give James a break folks. As far as I can see he stepped up and offered his services and has asked nothing in return, hell he even bought his own btcd.

The man has delivered before and I see no reason not to believe he will come through again. I for one would like to thank him as well as the rest of the dev team for there dedication and hard work.

Awesome stuff guys    

Today's shift payments have finished. Over 712 BTCD sent out to miners on all 3 algos!

Cheers!

Take a minute and read the payout details before deciding there is something wrong. Nothing is wrong. Don't be so skittish, it'll only hurt profitability. I'm not really sure how many more places I can put this information.

There are several way to contact me if you think there is a problem, use them next time before starting this kind of post.

Today's shift payments have finished. Over 712 BTCD has been sent out.

supporting vector types made some ripple effects.
For specifying inputs, it is now 9 dimensional!

lang, exchange, base, rel, botname, botid, signal, vector index and conditioner    

So I had  a bit of time packing the input type descriptor into 32 bits, but by storing (itemsize - 1) in the type, I was able to support vectors of up to 2048 elements with each item up to 256 bits. The 256 bitsize is important as there are many crypto data types that are 256 bits. If we need 512 bit fundamental types, i can always reduce the max vectorsize to 1024 elements

So, with this change propagating, it slows me down a bit to get all the inputs located, gathered and preprocessed

more a bit later

James

Why do I have over 800000 shares mined over the weekend and 0 confirmations on the official multipool? Bug? Should I not mine on the weekend? I thought it would all be sorted out for monday nights shift. Is the pool broken? Stopped mining for now as I just get more unconfirmed without even 1 confirmed. Miners be warned until explanation or fix.

To keep things simple I just support a single case of bitpacking, all inputs must be of the same size and none of them can be conditioned. This would require an extra bot layer to aggregate bitfields, but I think it is worth the savings of coding time as that is really the most likely use case

James

Just finished up defining the input/output process for the tradebots. Unfortunately it is getting a bit complicated for all the aspiring language creators, but the good news is the picoTradebotLanguage, PTL should be relatively easy to write, if you know C

Here are the data types for PTL:

structN - N bytes
bit[n] - N bits
['u']char[V] - 8 bits
['u']short[V] - 16 bits
['u']int[V] - 32 bits
['u']long[V] - 64 bits
['u']float[V] - 32 bits
['u']double[V] - 64 bits

All except struct ant bit types support unsigned. Yes, even floating point! On output, an unsigned float/double type automatically gets fabs() applied to it. The "struct" type is just an arbitrary number of bytes that will be allocated for output. bit[n] means "bit" or "bit1", or "bit2", etc. bit2 would be two bits, bit13 would be thirteen bits. For output having bitfields doesnt make much sense, but when it is used as inputs, then it starts making much more sense, as 32 "bit" inputs would fit into a single uint32_t

Now all the other scalar types have a [V], so you can do int4, int13, double16, etc. double16 is a vector of 16 doubles
Unfortunately this syntax has different meanings for the suffix, eg. N bytes or n bits or V elements, but hopefully it wont cause too much confusion.

A tradebot would register an output type with a name and it is responsible for keeping this updated.
So for input, you can specify the output of any other tradebot's outputs and due to the nature of the data stream it will be useful to modify the inputs, eg. SMA, EMA, filters, etc. So I have a "conditioner" field that will allow you to specify how an input field is conditioned and made available to your tradebot. This will be easily extensible to add a large variety of different signal processing algos.

I realized I have a bug in my bitpacking of inputs when they are not conditioned, so back to the coding I go. I fix that bug and start to create PTL callable functions. The power of this will become apparent soon

James

It is asset # 15344649963748848799 on NXT AE, currently at ~30 NXT or around $1.2 mil marketcap would be ~#30 on coinmarketcap

James

There is no big picture
I am just coding stuff

OK, so maybe it all fits together in a fantasically intricate self-reinforcing positive feedback loop that will create skynet, but I am not supposed to tell how this all turns out

James

I really didn't expect all the orders I set this morning to execute..... definitely not mad they did either.  10% increase in my coin supply..... Very nice 

Done!

support my request then: https://bitcointalksearch.org/topic/m.8017418

Looking forward to the future of this coin. So happy I have a few hundred of them and still buying up and trading to generate more and hold. Looks like BTCD has a bright future ahead of it and who knows maybe in the top 5 within a few months.

good on ya james. link to a wiki giving a "big picture" of how it all fits together might be good.

its great, how about a little information how to buy shares of instantDex? 

Fine with me..  go for it!

Is press release content OK?
If so, lets get some press

yeah, for example that BTCD will be rewritten by a longer version