Typical organofcorti genius stuff
When organofcorti visits your thread, it's like having the Pope come to your bingo game.
Something I'm curious about, though:
Is it "organ of corti", or "organov corti"?
Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 180. (Read 1151252 times)
January 18, 2016, 08:33:23 PM
Typical organofcorti genius stuff
When organofcorti visits your thread, it's like having the Pope come to your bingo game.
Something I'm curious about, though:
Is it "organ of corti", or "organov corti"?
January 18, 2016, 08:30:59 PM
Funny thing about Poisson Processes: Every day you don't stake, you still have 100,000 days to go.
Here's a fun thing:
Pick a random point in time, then:
A) the average amount of time from that point to the next CLAM block is 1 minute
B) the average amount of time from that point to the previous CLAM block is also 1 minute
C) the average time between CLAM blocks is also 1 minute
Wouldn't you expect A + B = C? Yet A, B, and C are all 1 minute.
I'm certain A) is correct, but not so sure about B). Isn't the previous block already fixed in time?
It is absurd that a random point in time would not have equal expected time difference with the previous and next blocks. How could that possibly happen? You could replay the blocks in reverse sequence, right?
The time between poisson events is exponentially distributed and "memoryless". It's defined nicely here: https://en.wikipedia.org/wiki/Exponential_distribution#Memorylessness. Since the process is memoryless the forward or reversed sequence of inter-block durations are just as likely as any other arbitrary sequence of the same inter-block durations.
I could well be making some kind of error of logic here, but:
* Pick any time random time, T.
* The expected time until the next block is always one minute.
* The time *since* the last block is always T - (time since last block).
* The time since last block is always known and is not always one minute.
* Therefore the expected time since the last block != the expected time until the next block.
Put all the blocks that have already happened on a line on a piece of paper, drawn to scale (scale = time). Now put another piece of paper on top and slowly slide the top paper to reveal the blocks. The expected time to reveal the next block is (always) one minute. If you stop at any random point and flip the paper over so the opposite set of points is hidden, and then start sliding in the opposite direction, the expected time to reveal a block at the moment when you flip the paper over is still one minute.
However, it is certainly true that like most logic "puzzles" the exact wording of the problem statement (and its interpretation if ambiguous) changes the answer.
EDIT: Interestingly, by the way, I think we had a very similar discussion a long time ago having to do with the Eligius payout method. My last sentence above likely applied to that discussion as well.
January 18, 2016, 08:26:12 PM
Funny thing about Poisson Processes: Every day you don't stake, you still have 100,000 days to go.
Here's a fun thing:
Pick a random point in time, then:
A) the average amount of time from that point to the next CLAM block is 1 minute
B) the average amount of time from that point to the previous CLAM block is also 1 minute
C) the average time between CLAM blocks is also 1 minute
Wouldn't you expect A + B = C? Yet A, B, and C are all 1 minute.
I'm certain A) is correct, but not so sure about B). Isn't the previous block already fixed in time?
It is absurd that a random point in time would not have equal expected time difference with the previous and next blocks. How could that possibly happen? You could replay the blocks in reverse sequence, right?
The time between poisson events is exponentially distributed and "memoryless". It's defined nicely here: https://en.wikipedia.org/wiki/Exponential_distribution#Memorylessness. Since the process is memoryless the forward or reversed sequence of inter-block durations are just as likely as any other arbitrary sequence of the same inter-block durations.
I could well be making some kind of error of logic here, but:
* Pick any time random time, T.
* The expected time until the next block is always one minute.
* The time *since* the last block is always T - (time since last block).
* The time since last block is always known and is not always one minute.
* Therefore the expected time since the last block != the expected time until the next block.
January 18, 2016, 06:50:20 PM
Funny thing about Poisson Processes: Every day you don't stake, you still have 100,000 days to go.
Here's a fun thing:
Pick a random point in time, then:
A) the average amount of time from that point to the next CLAM block is 1 minute
B) the average amount of time from that point to the previous CLAM block is also 1 minute
C) the average time between CLAM blocks is also 1 minute
Wouldn't you expect A + B = C? Yet A, B, and C are all 1 minute.
I'm certain A) is correct, but not so sure about B). Isn't the previous block already fixed in time?
It is absurd that a random point in time would not have equal expected time difference with the previous and next blocks. How could that possibly happen? You could replay the blocks in reverse sequence, right?
January 18, 2016, 06:44:14 PM
Funny thing about Poisson Processes: Every day you don't stake, you still have 100,000 days to go.
Here's a fun thing:
Pick a random point in time, then:
A) the average amount of time from that point to the next CLAM block is 1 minute
B) the average amount of time from that point to the previous CLAM block is also 1 minute
C) the average time between CLAM blocks is also 1 minute
Wouldn't you expect A + B = C? Yet A, B, and C are all 1 minute.
I'm certain A) is correct, but not so sure about B). Isn't the previous block already fixed in time?
January 18, 2016, 05:36:00 PM
Funny thing about Poisson Processes: Every day you don't stake, you still have 100,000 days to go.
Here's a fun thing:
Pick a random point in time, then:
A) the average amount of time from that point to the next CLAM block is 1 minute
B) the average amount of time from that point to the previous CLAM block is also 1 minute
C) the average time between CLAM blocks is also 1 minute
Wouldn't you expect A + B = C? Yet A, B, and C are all 1 minute.
I don't believe that's a valid equation for the problem.
The above is the kind of math politicians use...
If X is the time of the block picked.
A is the time of the next block
B is the time of the previous block
C is the average block time.
Then
(1+( ( ((X+A) + (X-B)) /2) - X)) = C
should give you C as the average block time.
EDIT: Even better if your already doing the time offset math.
(A+B) / 2 = C
January 18, 2016, 01:40:22 PM
Funny thing about Poisson Processes: Every day you don't stake, you still have 100,000 days to go.
Here's a fun thing:
Pick a random point in time, then:
A) the average amount of time from that point to the next CLAM block is 1 minute
B) the average amount of time from that point to the previous CLAM block is also 1 minute
C) the average time between CLAM blocks is also 1 minute
Wouldn't you expect A + B = C? Yet A, B, and C are all 1 minute.
January 18, 2016, 12:27:28 PM
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
Thanxs. Am I correct in thinking that in order for export to work, wallet needs to be sync'd?
I'm not sure what you are trying to do exactly. What do you mean by "export my transactions"? What is your goal?
It's a wallet feature under the 'file tab. Right below import. It's only available when in the transaction window.
To create a csv spreadsheet. Which can also be used as a tax record to calculate basis for capital gains/losses.
January 18, 2016, 10:37:58 AM
so I just need 0.01 CLAM for example and I'm good to go? or are my chances increased to process a block the larger my stash?
Your chance of staking per unit time is proportional to the size of your stash, yes.
If you have 1000 CLAMs you will stake 1 CLAM about once per day on average.
If you have 0.01 CLAMs you will stake 1 CLAM about every 100,000 days (or 274 years) on average although you might get lucky and stake on your first day of trying.
i only got 99,987 days to go!
Funny thing about Poisson Processes: Every day you don't stake, you still have 100,000 days to go.
January 18, 2016, 09:27:56 AM
so I just need 0.01 CLAM for example and I'm good to go? or are my chances increased to process a block the larger my stash?
Your chance of staking per unit time is proportional to the size of your stash, yes.
If you have 1000 CLAMs you will stake 1 CLAM about once per day on average.
If you have 0.01 CLAMs you will stake 1 CLAM about every 100,000 days (or 274 years) on average although you might get lucky and stake on your first day of trying.
i only got 99,987 days to go!
January 18, 2016, 03:50:24 AM
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
Thanxs. Am I correct in thinking that in order for export to work, wallet needs to be sync'd?
I'm not sure what you are trying to do exactly. What do you mean by "export my transactions"? What is your goal?
January 18, 2016, 12:00:55 AM
trying to sync up my wallet and have been stuck for 3 days now @ Wed Sep 30 17:58:40 2015. blocks : 665942
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
A few pages back is the bootstrap file that dooglus updates weekly. It will shorten your sync time to hours rather than days.
https://bitcointalksearch.org/topic/m.9772191 is the bootstrap post.
I update it whenever I remember it. The last time was about 12 hours ago I guess, so it's pretty up to date.
I don't know why the client gets stuck syncing the chain over the p2p network, but numerous people have reported that it does.
Xploited is working on a new version of the client which will hopefully fix the problem.
Thanxs. Am I correct in thinking that in order for export to work, wallet needs to be sync'd?
I believe so. Someone smarter than me can chime in, but I am fairly sure you can only export transactions that have all ready posted to the wallet. Any that have happened after the last week synced won't be available.
January 17, 2016, 09:57:04 PM
trying to sync up my wallet and have been stuck for 3 days now @ Wed Sep 30 17:58:40 2015. blocks : 665942
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
A few pages back is the bootstrap file that dooglus updates weekly. It will shorten your sync time to hours rather than days.
https://bitcointalksearch.org/topic/m.9772191 is the bootstrap post.
I update it whenever I remember it. The last time was about 12 hours ago I guess, so it's pretty up to date.
I don't know why the client gets stuck syncing the chain over the p2p network, but numerous people have reported that it does.
Xploited is working on a new version of the client which will hopefully fix the problem.
Thanxs. Am I correct in thinking that in order for export to work, wallet needs to be sync'd?
January 17, 2016, 06:34:29 PM
trying to sync up my wallet and have been stuck for 3 days now @ Wed Sep 30 17:58:40 2015. blocks : 665942
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
A few pages back is the bootstrap file that dooglus updates weekly. It will shorten your sync time to hours rather than days.
https://bitcointalksearch.org/topic/m.9772191 is the bootstrap post.
I update it whenever I remember it. The last time was about 12 hours ago I guess, so it's pretty up to date.
I don't know why the client gets stuck syncing the chain over the p2p network, but numerous people have reported that it does.
Xploited is working on a new version of the client which will hopefully fix the problem.
January 17, 2016, 05:53:33 PM
trying to sync up my wallet and have been stuck for 3 days now @ Wed Sep 30 17:58:40 2015. blocks : 665942
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
A few pages back is the bootstrap file that dooglus updates weekly. It will shorten your sync time to hours rather than days.
January 17, 2016, 02:44:41 PM
trying to sync up my wallet and have been stuck for 3 days now @ Wed Sep 30 17:58:40 2015. blocks : 665942
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
version: v1.4.17
connections: 4
wanted to export my transactions but it'll only do the 1st entry. Is that due to wallet not being fully sync'd ?
January 16, 2016, 03:57:10 AM
OK LADIES LAST ADVICE
SELL YOUR CLAMS NOW, THE PARTY IS OVER
SUB 0.001 BY THE END OF NEXT WEEK, MARK MY WORDS
REALLY, I'M NOT KIDDING
SELL YOUR CLAMS NOW, THE PARTY IS OVER
SUB 0.001 BY THE END OF NEXT WEEK, MARK MY WORDS
REALLY, I'M NOT KIDDING
So where should i put my buywall then?
Though i don't really see your words being true. I mean you are named VultureFund so what you want to do is holding clams. You can't profit from a dropping clamprice except someone lent out a big amount of clams to you. Which i would doubt.
So in fact i think you will buy cheap clams, that's all. You won't bother selling clams for a low price only to push the price down.
January 16, 2016, 03:54:14 AM
Thank you for clearing that up Dooglus and thank you for fixing the client to show the correct weight relative to the size of the stack.
Well, my first fix, back in September, left an empty column called "12":
And today I removed the empty column, so now there's no "weight" at all:
I figure there's no point showing the weight when it's just the same as the value in CLAMs.
Isn't the weight only the full clams? So 2.9353434 clams would have a weight where part of the weight calculation takes the amount of clams into account, but only as the full amount of clams on that address? Which means it would be 2 for 2.9... Or was it the value of the inputs on this address that were changed to integers?
Edit: Ah ok i see your previous post before my post. Seems it doesn't take integers. I wonder if i had this idea from another pos-coin.
January 15, 2016, 10:57:12 PM
Just wanted to follow up like a good BCTer and say that the transaction/wallet finally resolved: i have my clams. thanks!! was running in a vm, so maybe that caused the delay/issue.
Glad things worked out
January 15, 2016, 10:43:47 PM
Just wanted to follow up like a good BCTer and say that the transaction/wallet finally resolved: i have my clams. thanks!! was running in a vm, so maybe that caused the delay/issue.
Jump to: