|
With people wanting to buy and the current exchange still in maintenance,
I suggest we consider supporting private sales. It could be done in a number of ways:
1. Buy posting how many VGS you want to buy with direct PM by holders to
make the arrangements individually.
2. Through VGS using community funds with the BTC used to buy VGS set
aside in a separate address to be used for buy support when the exchange gets
up or another is added.
If someone wants an intermediary to complete the transfer of BTC and VGS,
I would be willing to provide that service, the only cost would be the actual
fee for the transfer of the BTC to the seller.
I have not run this by Vegasguy so, I am just throwing it out there for discussion.
|
|
|
|
Are masternodes working? How many are them?
Goal on Masternodes 12/31/17 per Vegas' previous post above (#810) |
|
|
|
|
Thanks for keeping this alive.
I was finally able to catch 1 of the
nodes you posted and sync up.
|
|
|
|
Which isn't going to help with Bottlecaps. From memory the relevant switches in Bottlecaps are splitthreshold and combinethreshold. The limits of these depend on where they are set, which is slightly mad. In the .conf or command line the max is (IIRC) 200/400 whilst via the RPC is walletbalance/500 and walletbalance/250 respectively. So to set these to maximum you would need to type into the debug window, splitthreshold 9999999999
and combinethreshold 9999999999 And repeat every time you restart the wallet. Alternatively you could have a script that sends the RPC commands at start up. Thanks for the correction. |
|
|
|
|
Have not been able to start this wallet for over a month.
Tried everything. Today it somehow started without crashing.
Had that happen one other time with a different coin.
Yeah!!!
|
|
|
|
Tranz made a change in HBN to make the split threshold to 2500. Let's hope he does the same for cap...
Nice. Considering the total number of coins the split treshold should be atleast 7500 for bottlecaps. This small change would make it much easier to stake. Hope Tranz have some time for caps soon.  I would agree... but 2500 would be an improvement over what it is now... 5000 or 7500 would be great... automation of everything leaves people, myself included, to just leave the wallet open all the time. Try putting splitstaketheshold=7500 into .conf file |
|
|
|
|
PickupCoin: Please PM Vegas directly. He is an expert at fixing individual wallet problems.
He has helped me many times on other coin's wallets when I had problems I could not fix.
|
|
|
|
Since the bottlecaps wallet requires a lot of resources it is probably best for most people to stake in a limited period of time. My strategy is to stake only once every 15-17 days. If you want to do this the inputs should be large, but not to large to avoid the 1000 coin cap. I get rewards from 500-800 coins this way.
I AGREE 100%. Big blocks that stake quickly but, not too big that you exceed the CAPs max. reward. 10,000 to 12,000 CAP blocks are a good size because if you forget to open when the block matures, the extra couple days should not put you over the max. reward. Don't forget that when you get a reward, it splits the block. A 12,000 CAP block becomes 2 - 6,000 CAP blocks (plus the POS). You need to combine blocks using coin control after they split to get ready for the next time. |
|
|
|
|
Only buy more if you believe the price will go higher or stay the same. If it keeps going down you will not make money which is the goal.
|
|
|
|
Hi, I'm interested in how adding coins slows down the maturity rate. Some wallets like 808 have different blocks that mature at different times, where it seems others just somehow combine all coins added into the same block. How does Bottlecaps work? I don't have a lot of coins so it adds time between stakes if I add more coins. I have more I bought at the exchange but don't want to slow down to the next reward if I can help it. Is there a block minting control somewhere that's harder to find?
If you have are hitting the max reward of 1,000 caps, it does not help to have more coins in a block. I think the formula allows for 15,500 coins to mature in 14 days and get the max. reward. If you had 100,000 coins in a block, you would still only get 1,000 caps rewards. If you are getting the max. reward in the minimum time, your coin blocks may be too large. Smaller blocks may take longer than the min. 14 days but, the interest rate is the same. So, 2 blocks of 7,500 coins at 28 days would get the same weight and be close to the maximum reward. Some people keep their wallet open all the time and spread their coins out so they get rewards every day. Some like a lot of blocks but, all maturing on the same day. That does not affect the interest rate. |
|
|
|
i stake my 1st 1.000 bottlecaps today, now i have to wait other 15 days to stake again 1.000 bottlecaps? i think if some developments are done for bottlecaps the price will rise. At the moment it stay the same price for long time, i not mind because i buy more but it is nice if dev work on bottlecaps.
Yes, you have to wait another 15 days. Hopefully someone will start to develop something for bottlecaps. A few sites back the former developer Tranz said that he would probably apply the same upgrades to bottlecaps that he are developing for hobonickels now. thank you, now i just open my wallet every day once a day to sync with the network then close until 15 days. Then i open it for how long it take to stake bottlecaps. i make 10.000 bottlecaps amounts so i try earn more stakes like people say in here. It should stake the same day. How long it takes depends on how many other wallets have big coin piles and are open. Might be 5 minutes or much longer. Depends on luck. |
|
|
|
|
Matt: Always such good and consistent info.
Thanks for all of your hard work!
|
|
|
|
my wallet is 5 days late and does not update, have a problem in my wallet or need to put some more node in the conf? thank you
Try these. addnode=68.134.228.254 addnode=96.237.153.160 addnode=76.106.178.142 addnode=85.214.152.3 addnode=144.76.237.39 If it does not sync, you may have gotten on a fork. Then, delete the appdata except wallet.dat and .config and re-sync |
|
|
|
|
Rewards Totals
The Marketing Rewards for the Week ending 10/01/17 are paid.
Totals for those participating in the Signature & Avatar Campaigns are
included in the totals.
|
|
|
|
|
Posts by Person By Date for Week of 09/25 to 10/01 Completed
Thank you!
|
|
|
|
|
Marketing for the week ending 10/01 is completed.
Thank you,
Woody
|
|
|
|
Is there any new addnodes, i try with new version of wallet, but stucked on 12076 block.
Here are my current nodes Addnode=85.214.152.3 Addnode=76.106.178.142 Addnode=96.237.153.160 Addnode=74.118.192.18 Addnode=188.68.52.172 If that does not help, you may be off on your own fork. In that case delete all in appdata except wallet.dat and.conf then, re-sync. That is what got me going when I was stuck. |
|
|
|
|
Zef - so you have have more than 1 address
Scroll down to see the other address(es).
Or click the arrow on the left to collapse the blocks
in the address showing.
Notice how small some of your block piles (input blocks) are.
You can click select all and, then, uncheck the larger ones.
By sending the small checked coins to yourself, you can make a
bigger block that will stake quicker.
|
|
|
|
|
I checked ports for all other wallets that are working and,
they all show closed on that site. The Fury wallet worked
perfectly for me till it didn't and nothing I have tried has worked.
I am going to leave it open for a couple days. If that does not
work, I will try on another computer.
|
|
|
|
debug file Fury version v12.2.1-Beta ()
Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
Startup time: 09/28/17 23:01:07
Default data directory C:\Users\Owner\AppData\Roaming\Fury
Used data directory C:\Users\Owner\AppData\Roaming\Fury
dbenv.open LogDir=C:\Users\Owner\AppData\Roaming\Fury\database ErrorFile=C:\Users\Owner\AppData\Roaming\Fury\db.log
Bound to [::]:6974
Bound to 0.0.0.0:6974
Loading block index...
Opening LevelDB in C:\Users\Owner\AppData\Roaming\Fury\txleveldb
Transaction index version is 70509
Opened LevelDB successfully
LoadBlockIndex(): hashBestChain=11e6d1af8db09caa4157 height=232790 trust=15077280436080755679 date=09/25/17 11:24:29
LoadBlockIndex(): synchronized checkpoint 30eefc3c1c721071afcd061ab8742c6c52c9cbc45bb209752362c0b060178e40
Verifying last 2500 blocks at level 1
block index 1841ms
Loading wallet...
nFileVersion = 1040201
Keys: 0 plaintext, 205 encrypted, 205 w/ metadata, 205 total
wallet 143ms
Rescanning last 21125 blocks (from block 211665)...
AddToWallet 6f0bc9d888
AddToWallet 87f6ae8755
rescan 672ms
Loading addresses...
Loaded 3 addresses from peers.dat 0ms
Flushing wallet.dat
Flushed wallet.dat 47ms
mapBlockIndex.size() = 233246
nBestHeight = 232790
setKeyPool.size() = 101
mapWallet.size() = 12337
mapAddressBook.size() = 4
Done loading
AddLocal([2600:8801:2904:774e:15e2:ffc8:75bf:6676]:6974,1)
AddLocal([2600:8801:2904:774e:fccb:e4e9:e58c:d0ab]:6974,1)
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
ThreadIRCSeed exited
ThreadMapPort started
ThreadSocketHandler started
ThreadOpenAddedConnections started
trying connection 76.106.178.142:6974 lastseen=390733.2hrs
ThreadOpenConnections started
ThreadMessageHandler started
ThreadStakeMiner started
ERROR: FetchInputs() : c36d01d955 mempool Tx prev not found 7baae6b0d2
Flushed 3 addresses to peers.dat 16ms
refreshWallet
trying connection 52.24.29.59:6974 lastseen=111.6hrs
ipcThread started
connection timeout
ERROR: GetMyExternalIP() : connection to 91.198.22.70:80 failed
connection timeout
GetMyExternalIP() received [] [::]:0
connection timeout
trying connection 78.46.92.72:6974 lastseen=390733.2hrs
GetMyExternalIP() received [68.224.101.145] 68.224.101.145:0
GetMyExternalIP() returned 68.224.101.145
AddLocal(68.224.101.145:6974,5)
trying connection 52.25.248.184:6974 lastseen=85.0hrs
No valid UPnP IGDs found
3 addresses found from DNS seeds
ThreadDNSAddressSeed exited
connection timeout
connection timeout
trying connection 93.99.96.155:6974 lastseen=390733.2hrs
trying connection 52.25.248.184:6974 lastseen=85.0hrs
connection timeout
connection timeout
trying connection 151.80.42.180:6974 lastseen=390733.2hrs
connected 151.80.42.180:6974
send version message: version 70002, blocks=232790, us=68.224.101.145:6974, them=151.80.42.180:6974, peer=151.80.42.180:6974
socket closed
disconnecting node 151.80.42.180:6974
trying connection 52.24.73.16:6974 lastseen=95.9hrs
connection timeout
trying connection 52.25.248.184:6974 lastseen=85.0hrs
connection timeout
trying connection 52.24.73.16:6974 lastseen=95.9hrs
connection timeout
Flush(false)
DBFlush(false) ended 0ms
StopNode()
ThreadMessageHandler exited
ThreadSocketHandler exited
ipcThread exited
ThreadOpenConnections exited
ThreadMapPort exited
ThreadStakeMiner exiting, 0 threads remaining
Flushed 3 addresses to peers.dat 0ms
Flush(true)
DBFlush(true) ended 0ms
Fury exited |
|
|
|
|
Show Posts
