Does this mean that older PoS clients are overriding the new hard fork? edit: difficulty back down to 0.00026726... I guess until the next network reversal  Yes this correct - this continue until one of the 2 conditions: - older PoS clients produce one more "bad"(invalid) block(same as cause fail of PoW mining) - it will be rejected by all new clients and make sync to old "PoS-only" chain impossible - new clients start produce more PoS blocks and will "outweigh" the old chain - new chain became primary/canonical |
|
|
|
Hi As I wrote few posts above: Fix will activates from block 412300.
At time at publishing new version at GitHub current block was 412109. Now (at writing this post ~5 hours later) current last block is 412131. So patch will activate tomorrow or in the next 2 days judging by the current rate of PoS blocks generation.
So enough time to download the source, check it, compile and synchronize with the current full blockchain without rushing before starting.
.....
Right now we are at block # 412255. So patch is not activated yet, need 45 more PoS blocks in original blockchain before PoW in new client kicks in and start "who have a longer dick chain?" game.  No any manual intervention is longer required - if the wallet is already synchronized with the mother-chain (to block number # >=412255) changes will apply automatically when chain reach block # 412300. |
|
|
|
|
MathiasW
if it first installation (or new in separate folder with separate database folder) try to add few first nodes manual
In data folder create (or edit if already existed) Orbitcoin.conf
and add some nodes:
addnode=203.45.89.214
addnode=95.27.219.139
addnode=178.27.212.144
After it restart client.
Seems orbitcoin has other bugs too and receiving the initial list if nodes after first/clean installation (when a local nodes list in peers.dat file is empty) through the IRC channel not working properly...
|
|
|
|
And now v.1.3.2 binaries for Windows: Orbitcoin_1.3.2By the way - if somebody start downloading blockchain from scratch (genesis block) and got stuck at some block (for example # 411229) - just restart program and blocks continue downloading. These are exactly the same "bad" blocks due to which PoW mining fail. The patch corrects error but it can not do anything with the blocks already included in the blockchain before. |
|
|
|
Finally new version(1.3.2) of OrbitCoin client with working patch to fix PoW mining. Source: https://github.com/MaxMaximus/OrbitcoinWindows binaries coming soon. Fix will activates from block 412300. At time at publishing new version at GitHub current block was 412109. Now (at writing this post ~5 hours later) current last block is 412131. So patch will activate tomorrow or in the next 2 days judging by the current rate of PoS blocks generation. So enough time to download the source, check it, compile and synchronize with the current full blockchain without rushing before starting. After block #412300 1.3.2 client will activate PoW mining but still continue syncing to current (buggy and PoS only) blockchain until one of the following conditions(what happen sooner): 1. Sufficient number of active miners miners (primarily PoS miners have value) switch to using the new version and be able to build longer (and with great PoS weight) chain compared to the old and be able to support it ahead of the old 2. In the old blockchain will appears next new "bad" block(incorrect blocks such as that are causing disruptions to PoW Mining now), which will be rejected by new client (because in it appropriate bug was fixed) and synchronize with the old chain will cease from this block. |
|
|
|
|
Got some free time and performed a detailed analysis and debugging code(requiring another full recompile of QT and all related libraries - about 10 hours only for full recompilation) associated with the patch.
Indeed - despite the fact that at first glance my patch and official patch do the same thing really big difference.
In the official version PoW Mining does not work at all: not only for now, but will NOT work after a few months (after the block 417000) too!.
So today or tomorrow I will once again update my version(it will be v.1.3.2) and go back to the original version of my PoW patch (as was in version 1.2.1).
|
|
|
|
Thx for your work Mad_Max, but i still cant solo mine...
"New" Orbitcoin-QT is still creating a 99.99% CPU state.
Is this normal at this time, the chaing getting broken?
Greetings.
Hi Stuck at 411665 (or 411666) block? Lol funny sitiation. My versions of fix (1.2.1) works and fix problem with PoW mining - i am try it myself + few other ppl - all work great - we me mine ~1300 block on. But was orphaned by PoS blocks from main (original) chain. Later more (~500-700) PoW blocks and so on. But later original developer (RedMist) do its own version of patch (with delay until block #417000). So later i make new version as fork from original - just replace # of blocks from distant future to close moment (from block #411650). And seem what official patch NOT fix situation! It works only to one next "buggy" block in blockchain and PoW fails again. Buggy block was #411665 (negative time spacing to prev #411664 again) - and PoW mining died again after this block. PoS still working (#411666 was my test PoS block). So if we stick to official client we just waste one or few month of time (before #417000) + work of people that will update the software to version 1.3 and shortly after #417000 network will stuck again and return to current situation. I do not know whether it was an accidental mistake or is it all a provocation initially (eg to undermine confidence in the currency and buy it cheaper, then to release a real patch and earn a Big on growing rate). I will look/test why original patch not solve problem later... If anybody know good coding and criptoclient can look at code Why this fix (my) if (nBestHeight >= NNNNNN && nActualSpacing < 0) nActualSpacing = 0; // patch to prevent negative nActualSpacing work (resume PoW mining) and this (official) int nHeight = pindexPrev->nHeight+1;
if (nHeight >= NNNNNN & nActualSpacing < 0) nActualSpacing = 0; //Sanity Check on nActualSpacing, corrects negative block values Not fix? NNNNNN - # of block there patch activates. In my quickie observations offical fix do pevent making buggy blocks by itself BUT if such blocks sent by other client (by older version or especially my some "pest") network fails again. |
|
|
|
By the way - original developer (RedMist) made his move. Seeing that patch like mine really works and solves the problem he stopped talking about the mythical attacks on its network and released its official version of the same patch (client ver 1.3.0). But to avoid version conflicts decide delay its activation to block >417000. That at the current rate will take a few months (since blocks are added only through PoS - and PoW is still not working without activation of the patch). And i place own version with with immediate patch effect. For this time i issued it according to all rules in the form of source code as fork from original code on GitHub: https://github.com/MaxMaximus/Orbitcoin |
|
|
|
Yeah tough. But who said that overtake hybrid PoW+PoS criptocoin should be easy? It is tough by design. Even such small and weak as OrbitCoin Although I think that now to establishment control enough to keep online (with temporarily unlocked wallet if it is encrypted, otherwise PoS generation does not work) about 3-5 wallets updated to new ver with coins (from 5 to 15 days had lain motionless) coming in by the middle-sized transactions to generate sufficient PoS blocks (more than in the current dying blockchain). So all who whant to try are welcome. Because of reward for PoS blocks in OrbitCoin set to 0% you have nothing to lose in any case - even if all of your blocks will then be canceled/orphaned in the end. But with PoW mining decide for yourself - if new chain fail the whole chain of spend work/electricity lost. |
|
|
|
Yes lot of new blocks was orphaned.(almost all) REORGANIZE
REORGANIZE: Disconnect 1354 blocks; c4eacae0919a7b7d9339..0000002aa34a235c528d
REORGANIZE: Connect 16 blocks; c4eacae0919a7b7d9339..fa732229effe372f145a But NO it is not new fork. It is revert to original blockchain. It because I am NOT banned old original clients (1.0 and 1.2) for now in my version. We can sync both to old and new clients now(while old can sync to old only and ignore blocks from new). So our entire new blockchain was orphaned by main chain (stuck one - without PoW) because PoS blocks have much MUCH more weight in OrbitCoin. (near x 1 000 000) So client synс to main PoS chain and start building new chain from it again. To prevent this happend again and again we need PoS miner with new updated wallets to generate enough own PoS blocks in new blockchain. I connect my own PoS wallet with ~ 5000 coins, but it still not enough to overweight old chain. My wallet produce 15 PoS blocks in new chain today. After old chain accumulated >15 PoS blocks my 15 PoS (+ all PoW >1300 blocks) was orphaned. So please stop PoW mining at new chain for now - it's a waste of resources at the moment because all PoW mined blocks can be canceled at any time by few PoS blocks. We need critical mass of PoS miners in new chain first! |
|
|
|
Very tired now so I'm having a quick look and trying to understand the problem. Is it as simple as the time of two adjacent blocks being out of sequence, the more recent one having an older time, resulting in a negative number when calculating the last time period? 31-Dec-2013 13:56:33 height: 411227 mint: 0.25 difficulty: 0.17286038 flags: proof-of-work
31-Dec-2013 14:56:05 height: 411228 mint: 0.25 difficulty: 0.17353002 flags: proof-of-work
31-Dec-2013 13:58:21 height: 411229 mint: 0.25 difficulty: 0.05879355 flags: proof-of-work
31-Dec-2013 14:07:36 height: 411230 mint: 0 difficulty: 0.00024414 flags: proof-of-stake
So somehow a block which based on timestamp should have been around #411235 ended up in the blockchain at #41228. The next block was the final PoW one. That's enough to cause the network to get stuck? I can see the same thing happened to CDC earlier this morning. Is this a hard fork where EVERYONE will need to update their client in order to mine, or will it be sufficient for the majority of the network to update? Yes - wrong timestamps of blocks - is a part of conditions to trigger bug. But PoS involved too - of no PoS blocks mined at same time - wrong PoW blocks will be just orphaned and situation selfcorrected after some time (few hours MAX). But with PoS block at same time (and without full check in PoS gen code) wrong PoW blocks are sealed in the blockchain and can not be orphaned by PoW miner (it can be orphaned by other PoS miners but they do not do so as PoS code does not see any problem in such blocks and regard them as valid) About fork. Actually we have 2 options: fork from 411227 block then only majority of miners(PoS miners mainly) need to update. After miners with updated client build longes chain (compared to stuck one) on all other(not updated) clients all blocks after 411227 will be orphaned and replaced by new chain without invalid blocks automatically. Without any soft updates. And my first patch was this version - i just BAN (blacklist) block 411228 and rebuild blockchain - PoW mining start normal working from 411227 block. But later I refused this option - because it creating a large number of orphan PoS blocks (which can include some real important transaction for the last 5-6 days) + this variant need a large number of PoS miners with large amounts of coins in stack to quickly generate at least 400-500 PoS blocks and overtake the current chain + this NOT prevent such bugs again in future. In second patch i remove block ban and add simple check for negative time spacing. No need to orphan current blockchain, but all will need to update because old clients not accept blocks from new (even if it from longest chain). If not all update clients it will lead to blockchain fork to 2 parallel chains. So it is some sort of hardfork now... |
|
|
|
Will do full github fork later. But main (only necessary) patch is very simple. You can do it youself: just open src/main.cpp find this function: unsigned int static GetNextTargetRequired and add code: int64 nActualSpacing = pindexPrev->GetBlockTime() - pindexPrevPrev->GetBlockTime();
if (nBestHeight >= 411228 && nActualSpacing < 0) nActualSpacing = 0; // patch to prevent negative nActualSpacing
And compile. If you can connect to my node and sync to ~412100 blocks(>19 billion trust score) or more - you do all right  Bacup wallet.dat ofcourse before try. I make few other minor updates (like protocol and client version info update) - but they all are optional. 411228 - is last normal block before PoW is broken. Initially i think we need fork blockchain from it... But i try start mining from latest PoS block - and it works too. So no need to orphan last ~300 PoS bloks (it may include some real transactions) |
|
|
|
YES - it is not OrbitCoin exclusive bug. It was inherited from the previous forks. Just need some rare confluence of conditions for its manifestation. Bay the way. After of few days of compiling and debugging i finaly patch code and successfully compile/build it under Windows! My small patch is working - i can mining (PoW) normal now. (I am at 411847 block already - started from current last PoW block 411577 ) But all need to apply this patch or network will be forked. (2 exchanges and block explorer - most important part) Here is my new (1.2.1) version of OrbitCoin client: Windows binary: http://yadi.sk/d/8BiaEltqFR844For those who want to see the all changes in code and try to compile yourself i will try make fork on GitHub (although I have never done that yet, and even there is not registered) P.S. To all - do NOT make any transaction now - until it is not clear which of the forks win. |
|
|
|
|
2 almightyruler
No this changes activates only after 1051200 (1 mil) blocks. But now we at ~410k blocks only. Some bugs it in POS realisation part (Inherited from BitBar/YAcoin or even from NovaCoin or PPCcoin - not sure ORB was forked from, some sight in code point to NovaCoin, but may be fork of the fork of fork...) - sometimes (in some rare situations) POS produce buggy(incorrect) block but it pass check and not rejected/orphaned but included in blockchain.
After this monent all other PoW bloks will be regarded as invalid and rejected - only PoS accepted.
P.S.
After many hours I could finally build it under windows. But now it crash just after start...
Will try recompile QT itself + boost from source next time before compile client. But it so looong and slow...
|
|
|
|
No working pools and solomine not work too (at all = 100% rejects). 5th day now Although transactions are still going through - but only at the rare POS blocks. (if there was no POS generation network would already be dead) I think i can temporaly fix network (it is a buggy code, although the original developer thinks that this some kind of attack on network and conspiracy against him ). But i even cannot compile it from sourse: on the official site only binary files. And source at https://github.com/Orbitcoin/Orbitcoin not compile - lot of random errors (wrong path, wrong includes, wrong functions call from libs etc). Think it is not same version from which it was current binaries for windows created... I Try both console deamon and full GUI QT wallet. MinGW 4.8.1 QT 4.8.5 boost (source of majority of problems at compiling) boost_1_43, boost_1_50 / boost_1_53 / boost_1_55 db-4.8.30.NC openssl-1.0.1 |
|
|
|
|
I doubt that there was an attempt to scams
But I can confirm BIG problems with support and admin reaction to problems/errors - all last weeks almost all tickets/e-mails/PMs from clients just are completely ignored.
For example i have some problems with access to my own account (due to some unknown technical problems confirmation codes do not come to my e-mail and because of what i can not pass the 2th authorization stage and log in to my account). It is a critical issue - i am de facto bloked and lost control of all assets(USD, BTC, LTC, PPC and few shares) placed on this exchange with total value of few BTC for more than a month.
During this month I sent a few tickets, direct e-mail and a post on this forum(in the official theme of the exchange) about this issue - and not got ANY reactions from support/admin.
At the end(after several weeks of waiting and polite requests) i began to "bomb" all known contacts by e-mails with headlines like "Stop ignoring critical issues!" or "Begin to respond or be labeled as scammers!" and finally was able to attract the attention of someone from support. But it was only 2 lines - a short apologies and please remind "what is the problem"? (although in my letter it has already been described). And after my answer with a more detailed description of situation - no any reactions again (one more week pass).
Fortunately, while I was waiting for reaction one of the verification codes could slip to old e-mail after my numerous attempts to login, I managed to login one time and use it to immediately change e-mail address and disable e-mail verification codes. I now have normal access to the account cuz i solved the problem myself.
|
|
|
|
По криптовалютам разумеется в законах ничего отдельно не сказано пока. Поэтому предположительно на общих основаниях как ценные бумаги(акции, облигации, фьючерсы и т.д.) - суммарная выручка от продажи минус все расходы на их приобретение и непосредственно связанные с этим (например комиссии биржи/брокера при покупке/продаже). Что грубо говоря дает 13% от чистой полученной прибыли. То что брокер ничего не просчитывает с точки закона ничего не меняет. У "больших" брокеров являющихся налоговыми агентами это сделано для удобства и упрощения работы для клиента (и лучшего контроля для налоговой), если брокер этого не делает то человек сам должен это проделать при подаче налоговой декларации. (аналогично тому как работодатель по основному месту работы делает это за своих наемных работников, хотя по-идее это обязанность самого работника) Я сам налоги с крипты правда еще ни разу не платил - т.к. криптой торгую только 1й год, соответственно налог с нее нужно будет платить 1й раз еще только будущей весной (точнее подать декларацию, а уплата до лета 2014го). Я как раз про обычные биржи говорил (на которых уже много лет торгую) и где всю техническую часть делает за тебя брокер, остается потом только указанную сумму оплатить (или он сам же и заплатит если на счету достаточное кол-во свободного кэша оставить когда период платежей подойдет). Как это правильно с криптой оформить мне самому интересно. Представляю выражение лица налогового инспектора если я в графу прочие доходы впишу "операции с криптовалютой", и к декларации приложу скажем расчет со всей историей сделок на BTC-E за год. Которая у меня занимает уже больше 40 листов (в основном из-за чертовых ботов, которые переодически любят на 1 крупный ордер анонировать пачками сделок скажем по 10 руб или по 1$, бывает десятками, а иногда и сотню мелких сделок в один ордер насыпят) Но насчет налогов надо бы наверно отдельную тему где-нибудь завести. К Битстампу вопрос никакого отношения не имеет совсем... Я собственно не про налоги хотел писать, а про коммерческую деятельность. Что доходы (и налоги с них) совсем не синоним коммерческой/предпринимательской деятельности. Они могут быть связаны с ней, а могут быть и нет. И когда я получаю(или наоборот отправляю) деньги выведенные с биржи (что с обычной - например с ММВБ, что с крипто), я тоже(как и SergKaac) с чистой совестью ставлю галку и подпись напротив пункта "данный перевод не связан с осуществлением мной предпринимательской деятельности". Т.к. предпринимательской деятельности на самом деле нет (несмотря на то что доход все же есть). |
|
|
|
Жестко сказано, но суть думаю верна.
Математические расчеты на компьютере, вряд ли отличаются в НК от того же программирования.
А получение доходов с этого, вполне себе , коммерческая деятельность.
Или не так ?
Не так. У коммерческой (предпринимательской) деятельности отдельное определение. Могут быть доходы как связанные с коммерческой деятельностью, так и не связанные. Например я торгую на бирже и получаю от этого прибыль (от игры на разнице курсов/цен ценных бумаг), получаю от этого доход. Плачу с этого полученного дохода налог каждый год. Но при этом все это НЕ является коммерческой деятельностью по нашим законам. Просто доходы физ.лица и обычный налог по ставке 13%. Регистрации юр. лица или ИП так же не требуется. |
|
|
|
|
Show Posts
Don't hold much hope, over in the Stablecoin thread there have been about 4 new releases over the past 6 months, some peers are still running the original client!
