There're only 120*250=30k mature coins and there're at least 50k+ buy offer  Demand is too much. I'm not gonna regret to mine this coin  |
|
|
|
lol that guy @ 25 gh on suprnova paying 0.41/gh
It's gonna end in half hour; My order is waiting his order to finish I'm gonna mine it too, yes! It was a long time to mine an altcoin  |
|
|
|
This is just an idea. try to spark some creativity in this forum. You can not do it without centralized pools etc. Beside spreadcoin similar idea was used before on minerals. What happened to it? Big farms/ASICs?
Hashing power of each worker and/or IP will be limited to not more than 50 MH/s (see the poll) by limiting the number of shares that a worker can send to the pool per unit of time. https://bitcointalk.org/index.php?topic=641057.0 |
|
|
|
|
That one looks good. But I didn't like only one thing;
Why is the topic self moderated?
|
|
|
|
|
What's the 1000 ghs's type? Is it all from S5's?
If it's all s5's then you can sell those ghs's on market for over 1.4BTC.
Why're you selling that account that cheap? it seems fishy...
|
|
|
|
Ok guys.. new investor here. Whats the story, anyone wanna run down for me what this coin has done so far, whats under construction and what's to come.
If you're here; then we may assume it's gonna be pumped hard  |
|
|
|
I bet this coin will be broken.
Chain won't accept pow blocks after pos starts.
As I'm always saying that don't start pos during pow. Let's wait and see if I'm true or not.
Anyone here to confirm what I wrote? Seems it was broken for some time |
|
|
|
|
2nd of June 1KGebemVM3i5DwWoU5fp5VkV7ZhKKcxjpK
|
|
|
|
It's not about percentage. It's about excluding tx's from "all" tx pools. That's the only way.
Even if all of the miners exclude spesific address's tx's then those people can edit their mining pools & tx pools to accept only those tx's to create block. If they're lucky enough they'll create block and their tx's will be on the chain.
In your scenario, the txs may be put in a block, but the block will be rejected by other miners and orphaned. How will they orphan it? if it's a block that has all requirements of network, miners can not reject it. Also it's not their choice to make a block orphan. They certainly can reject it. If they don't consider the block to be valid because it contains an invalid transaction (the blacklisted one), they continue the chain from a different block and that one is orphaned. If they want to reject & orphan it they have to find a block with same height at the same time which is acceptable by the network. |
|
|
|
None of the links in OP is hidden with that logic. The only hidden page to normal members is Staff Forum. I'm gonna prove you're wrong As a normal member I don't know where's that section and I really want to know what's spoken on there... Proof from Badbear: There's a subforum that is only visible to donators.
edit: that section's link: https://bitcointalk.org/index.php?board=68.0 |
|
|
|
|
I can enter the contest but how will you provide fairness? How will we know that you didn't give the prices to people you know?
Also I don't want my full name published by you.
|
|
|
|
Sorry for the long silence, it takes time to sort out things like this. As per our usual response, if we detect something wrong with a blockchain where the dev _might_ be involved, I like to post a public statement so everyone has the same information at the same time. Exchanges were informed earlier today when our security measures kicked off.
There seems to be a problem with the "lucky" staking code from what we can tell at this time. There are blocks that were accepted with POS rewards up to 3.3M which is why outside the rate for the coin. Additionally, as of right now there are way more coins in existence than the wallet thinks there should be:
"balance" : 24751980.90800208,
"stake" : 0.00000000,
"blocks" : 4655,
"timeoffset" : 0,
"moneysupply" : 21073266.40374496,
This is our current supply. C-Cex and yobit have another combined 5-6M. At this time, we don't know if this is malicious or an error in the staking code. We have cancelled all orders on the market and closed the wallet for the time being. If the devs can please contact us and come up with a solution, we will reopen the market. If we an agreed solution cannot be agreed upon, we will close the market and open the wallet for withdrawal only.
thanks,
richie@bittrex
That seems like another coin with broken PoS thing, check here: https://bitcointalk.org/index.php?topic=1001062.msg10956175#msg10956175I bet those 2 coins's dev are related. |
|
|
|
It's not about percentage. It's about excluding tx's from "all" tx pools. That's the only way.
Even if all of the miners exclude spesific address's tx's then those people can edit their mining pools & tx pools to accept only those tx's to create block. If they're lucky enough they'll create block and their tx's will be on the chain.
In your scenario, the txs may be put in a block, but the block will be rejected by other miners and orphaned. How will they orphan it? if it's a block that has all requirements of network, miners can not reject it. Also it's not their choice to make a block orphan. |
|
|
|
Ring signatures and Masternodes are together? What do you think about that Darkcoin and Monero fans? |
|
|
|
What are you even talking about? The threads I've opened in meta are relevant, not just some useless bickering about "he has more power than I, why!!1!, remove him from default trust, he is a ponzi guy, he is a scammer, remove my trust". These things shouldn't be in meta. You know exactly what I'm talking about, if you didn't get it; let me be more clear. 2 years ago you "told people bitcointalk is back on bitcointalk" dude that's really wise! https://bitcointalk.org/index.php?topic=306717.0Just 1 year ago you opened a thread about "remove my trust": https://bitcointalk.org/index.php?topic=585285.0Just 2 weeks ago you opened a thread about "scammer": https://bitcointalk.org/index.php?topic=1028939.0 And yes it was too relevant about meta so it wasn't moved *sigh*. Please be more consistent. |
|
|
|
I've blamed 12 times and now it's 170 (ps: for firefox "ctrl + shift + p" (for chrome "ctrl + shift + n") and blame again and again and again.) |
|
|
|
|
Show Posts
