@haitch i just created a db from scratch using 1.2.8 , it is right now 12376460 (12GB)
database file was 14 GB just after it had been built, database probably does some cleanup once the wallet stops pounding it with records.
my other older wallet, also 1.2.8, also up to date, is at 6GB but i'm not sure how that db was created, it could've been created using an older wallet, perhaps data is sent in a slightly different format from 1.2.8 i don't know.
What you see is new transactions that are known by your wallet but not yet in any block. It is transactions from all over the burst network, and if you look at it for a while, you will notice that when a new block gets created somewhere, then the list of unconfirmed becomes nearly empty or entirely empty bc they were put into the block.
burst has been running since 2014 and nobody i know of has been able to steal any burst, except by getting hold of the owners passphrase - as long as you don't let anyone steal your passphrase, your coins are safe.
@theduuude I find it ...interesting....
right now, it would be hard to get out of a big position without moving the price a lot down.
perhaps the lower volue and price is related to crowetic leaving, perhaps not many ppl want to buy in expensively in case some burst is planned to be sold in relation to winding down stuff.
i, for one, don't have any limit orders in, i'm in a wait and see mode, i don't want to risk being a bagholder in the short term. i don't want to be run over by selling pressure from people leaving burst.
if this is a shortterm blip (and i think it is) great trading opportunities are building up.
As I reemember it, before bitsler was announced, we came from 600+, turned around in the 380s before shooting for 800. ( these numbers are from memory, so i could be off 100 or more)
@mrgoldy As far as i know, plotschecker only checks the file size, compared with the information in the filename.
xplotter (i think) plots with file size = stagger size, so i assume it writes the entire file at once, and then seeks around to put in the nonces as they are created. I would assume that plotschecker cannot figure if the file is okay or not, cause the file size would then be fine in relation to stagger, even though the information in it is not yet fine.
@crowetic
I'm trying to increase my TB, but i think we need more ppl in the pool to hit blocks more often. I'll probably stall around 132TB in a day or so, having run out of stuff to plot. It should be good for about 2 blocks a day, but it's more fun if we could get like 4 or 5.
Other than that it seems like smooth sailing, the user experience so far is that stuff is working like it should.
I have 4 pcs running a miner with various plots, i hope it is not a problem that one pc might send a deadline that is lower than something one of the other pcs might have sent. Also hope there is no penalty for that, as long as it's just bc i'm running from several pcs.
We just hit 2 blocks, now you have a chance to check logs with blocks winnings and payouts and stuff
Good to see payouts buffering raised to 500 burst / 300 blocks. No need to pay all those fees.
@iKnow0
the value of an asset depends on the nature of the asset.
Is the asset like a performance bond, where you get a periodic payout , and at some point in the future the asset is bought back by a big payout followed by no value to owners after that?
is the asset a dividend stream with no final payout (so more like a bond that never gets redeemed)
Do the asset ownership entail ownership some of the assets of the issuer? Is there a way to hand in the asset, and get title to the assets, or get settled monetarily?
is the asset owner bound to pay dividends on a fixed percentage of income, or is the income fixed in numbers, and any additional economic value in the "asset-company" go to the "owner/issuer", not "asset owner/lender/investor"
When that is sorted out, you can decide on a future real interest rate curve, measured in some currency (fiat or burst) and determine expected future payouts far into the future, and then calculate the net present value, under the assumption of the future real interest curve.
when net present value has been calculated,
you could do a share buyback , and then re-calculate net present value for the shares left outstanding.
buyback was only a good thing for the remaining owners, if the re-calculated net present value is higher than the pr-buy back net present value.
So it seems the NAV is subject to some objective estimates on future real interest rates , and therefor impossible to get exactly right.
Still, it is of course possible, and perhaps beneficial for an asset to have put in a scheme for buying back assets at a price lower than some estimated NAV - both as a service to asset holders who wants out at some specific time, and as a service to the asset holders who hang on, who then get a higher estimated NAV going forward (basically higher expected future payouts plus redemption value)
You would have to adjust any limit orders as burst price rise and fall, or else your buy prices might suddenly be too generous if burst price is up a lot.
i'm thinking something along these lines :
(the 0.6 is an example)
You could also put in sells at buffer = 1.4 or someplace else in overvalued-land
Because burst tends to move a lot in price, you need a big buffer or you need to monitor and update prices regulariy, or you need to make the bids and asks only small positions, or you need to change the scheme into market buying and selling at the time NAV is calculated, and not as a floor/ceiling limit order that stay on as NAV drifts around after having been calculated.