same thing - started at 1 connection then went to zero
and it just sits
tried running it as administrator and same problem - stuck with no connections
but I think the 1 connection is false because it cycles through 1 and back to none over and over
Must be something wrong with your machine or local network. Try ping/tracert to these seed nodes, maybe another machine/notebook or VM. |
|
|
|
thanks for the info - firewall is completely open
running on windows8
no connections at all - zippo - nada!
all other wallets on the same computer are connecting fine
Put the following in your data/orbitcoin.conf if nothing else works for you. dns=1
addnode=seed0.orb.sx:15298
addnode=seed1.orb.sx:15298
|
|
|
|
does anyone have a .conf file?
my wallet won't synch - no connections.
You get addresses from DNS seeds + IRC. That's enough to get started. well my dns works fine because they're my dns servers I have 6 of them and two only do authoritative look ups. These are not DNS to resolve domain names into IPs. These are core servers to give out lists of client addresses. These servers have their names listed in every wallet. Make sure your firewall doesn't block orbitcoin-qt.exe and you have port 15298 forwarded properly on your router if it doesn't support UPnP. I have just started the client in a clean VM and got 12 connections in a couple of minutes without any forced addnodes. I have 43 credits of 2 ORB each and all on 11/05/14 with the last one at 12:19. It is now past 9 days and I have now POS reward.
When I hover of the staking symbol it says:
Staking enabled for 43 inputs weighing 382 coin days.
Do i have to wait until 387 coin days (43*9=387) for a POS reward?
No, that's a cumulative weight of your wallet just for reference. About 10 coin days per input, not much actually. A particular input has good chances of staking at the lowest network difficulty with weight ~100. Higher the difficulty, more weight needed. You can see what inputs/weights you have in the Coin Control (Settings->Options->Display to enable). |
|
|
|
does anyone have a .conf file?
my wallet won't synch - no connections.
You get addresses from DNS seeds + IRC. That's enough to get started. |
|
|
|
|
v1.4.2.1 uploaded. Optimised staking for small inputs, addnode and getaddednodeinfo RPC commands implemented, byte counters for getpeerinfo added. This is an optional upgrade.
|
|
|
|
Initially diff was 0.0002 and inputs around 80-90 weight were staking reliably as soon as they got 9 days old.
Ghostlander, are inputs now able to stake after 5 days?
Inputs produced after block #650K stake after 5 days. Older inputs stake after 9 days. |
|
|
|
Yes, i re-download entire database from scratch after upgrading from 1.4.1 to 1.4.2. (BTW this time it was significantly faster ~ 8-9 hours instead of ~ 20 hours with 1.4.1 and i notice what it use second CPU core from time to time, not strict 1 core as was with 1.4.1. You already add partial multi-threading support?)
I have reduced message polling latency from conservative 100ms to fast 20ms and disabled the ACP checks during initial block chain downloads. Now orb-msghand thread processes data fast enough to keep up with orb-net thread supplying it. |
|
|
|
Can you upload recompiled binaries with this last patch? Or may be better if someone tell what could be the cause of the error in my own compiled version:
I compile 1.4.1 myself and it work fine(and prev 1.3.0 and 1.3.2 OK too), but with 1.4.2 i am getting errors for some unknown reason (i use exactly same compiler and external libs only replace ORB source and libs included with it like levelDB).
I'll make one or two additional patches before releasing an update. Have you re-built the transaction data base after switching to v1.4.2.0 by bootstrapping or re-downloading? The old one lacks metadata needed by the new code, so it throws exceptions and crashes. |
|
|
|
The current code tries to combine inputs only if generating input is above split age (nStakeMinAge + nStakeMaxAge). It is the only condition when txNew.vout.size() == 2. The 1st vout is reserved always. vout.size() == 2 means one actual output. vout.size() == 3 means two actual outputs, i.e. stake split. This patch fixes this issue as well as stake splits to amounts below the combining threshold. This kind of fragmentation isn't necessary. Inputs less than 50 ORB won't be halved. Works fine. So i not understand why we need this check about 2 outputs?
This requirement comes from PPC. The reasons behind it are unclear, so you may want to ask Sunny King. Maybe he didn't want input combining to work our way, though PPC uses this feature very occasionally as there is no generation threshold. Even if a generating input is very small and there is nothing available to combine it with, a PoS block is produced still. |
|
|
|
These are my thoughts:
1. keep the hard cap (this is VERY IMPORTANT)
There is no hard cap. It is an illusion. It is only possible with fixed rewards for both PoW and PoS + no fee destruction. Something like Orbitcoin does now. |
|
|
|
I notice what "bug" with coins actually start staking only after 9 days (instead of 5 days) apply not only to stake kernels but for additional inputs too.
e.g. if small (< 20 ORBs) but with relative hight weight(old coins) inputs generates PoS it search for other inputs to add up to >= 20 ORBs before can produce normal PoS blocks .
By design minimum age for such additional inputs is 5 days too. But in practice (in current v 1.4.1) it not work - wallet can use only old (~10 days or more) inputs for this. In situation when at same adress(key) lays smal old (10-15 days or more) inputs and larger younger(5-9 days) inputs it produce error about stake amount below the minimum
It is a same bug and is this fixed in 1.4.2 ? If not i think is not too late to fix it before hardfork at #650000
Must be the same bug. It's one day left until the hard fork, not good to rush with additional changes. Even if it doesn't, we can fix it later without a hard fork. |
|
|
|
I meant that the local copy of the blockchain would need to be rebuilt from scratch.
Just concerned that there have been two versions requiring hard forks in such a short period. I missed the last hard fork by a few days so I had to reset/restart my local db.
A local copy of the block chain is the same (actual data in .orbitcoin/blocks and index in .orbitcoin/blktree). Metadata for future transaction pruning was added to transaction data base (.orbitcoin/coins) making it incompatible with the previous releases. Are Cryptsy on board with the latest version? Yes, they are. |
|
|
|
|
NVC is much different now from what it used to be a year ago. Decide where you want to go with PoW and PoS first.
|
|
|
|
Orbitcoin v1.4.2.0 is available now. A hard fork at block #650K, many improvements. Please upgrade in time.
Due to changes to transaction data base, block chain re-download is necessary. Deploy your new client to a separate location and use bootstrap.dat or let it synchronise on its own.
So those who upgraded to v1.4.1.0 only two weeks ago need to upgrade again, plus restart the blockchain from scratch?  The block chain is not restarted. The initial support for pruned transactions appeared in v1.4.0.0 with the CCoins* class functions. It's extended now to actual data serialisation. Failed transactions are also detected and managed properly now. Incorrect interval of stake modifiers has been fixed finally, though this issue existed since the coin launch, but no one cared to find out why all coins are staking after 9 days instead of 5 days by design. There is enough time for every user to upgrade. |
|
|
|
|
Orbitcoin v1.4.2.0 is available now. A hard fork at block #650K, many improvements. Please upgrade in time.
Due to changes to transaction data base, block chain re-download is necessary. Deploy your new client to a separate location and use bootstrap.dat or let it synchronise on its own.
|
|
|
|
I'll provide a 5% discount for payment in ORB at Amazonia Imports http://btcpipeshop.com/ for the next month if that helps. The discount is configured within coinpayments 'coin acceptance settings' so the price you see is the discounted price. Thanks, advertised in the ORB forum. |
|
|
|
Those running KGW might want to take a look and my commit for BOB's Wormhole, and possibly adapt it to their own coin, if they still plan to keep it KGW. That is if no one finds its flaws are worse than stock. BOB's Wormh0le - Kimoto Gravity Well CustomizationThis glorious patch has changed 2 lines of the actual code to make it fit your very slow coin and 1 more line to narrow event horizons. Now, it's surely the greatest thing since tinned beer. Or not? It's still KGW and it's still broken, time warping not fixed, but you don't get it anyway because you haven't cared to read this thread from the start before posting your advertising spam.  |
|
|
|
We never got paid to list ORB. We use public votes, not bribes.
ORB was one of 14 coins you selected for the public beta before any public votes started. I admit Red Mist has failed to deliver what he has promised, but the community is still there helping to make something good. Give it a couple more months and remove if it doesn't work out. Yeah, that's right, we still didn't receive any payment for it though. We'll turn it back on for another 2 months, but if it still isn't getting any transactions I don't want to hear any complaints if it gets turned off  Fair enough, thanks. |
|
|
|
We never got paid to list ORB. We use public votes, not bribes.
ORB was one of 14 coins you selected for the public beta before any public votes started. I admit Red Mist has failed to deliver what he has promised, but the community is still there helping to make something good. Give it a couple more months and remove if it doesn't work out. |
|
|
|
|
Show Posts
