Amoveo ♥🧿
Previous messages
Next messages
23 March 2018
OK
01:02
O K
Man...
IP
01:05
I P
so what do we do?
MF
01:05
Mr Flintstone
ugh why aren’t they paying attention to this telegram chat
OK
01:05
O K
Well they might be
MF
01:05
Mr Flintstone
if they are, then they just want the block rewards I guess
OK
01:05
O K
It would help to know if there is a max fork length
MH
01:05
Mandel Hoff
I think we hope to stay ahead of them until we reach the max fork length recovery - I recall it might be 20 blocks, but not sure. Zack could confirm.
IP
01:06
and they lose all funds for not cooperating with the community
OK
01:06
O K
I'm not concerned so much about losing blocks, as with that they are nearly equal hashrate, and just behind the longer chain
MH
01:07
Mandel Hoff
The very immediate threat is that our nodes would throw away the last 14 blocks and take their fork if they jump ahead.
MF
01:07
Mr Flintstone
Yeah
01:07
FYI don’t do any important transactions right now if that wasn’t obvious
OK
01:07
O K
👍
I
01:09
Iridescence
Good old dominating hashpower
OK
01:10
O K
2 blocks now
01:10
since 16 blocks
01:16
So, if we pass the max fork length, there will be Amovirgina and Amoveo forks ?
01:17
We could double our monies guys 😂
P|
01:18
like .. they have male and female and xxx?
MH
01:18
Mandel Hoff
I see a variable in the code called fork_tolerance that is set to 50.
OK
01:18
O K
😂
01:19
50 is quite long
01:19
That could do a lot of damage to someone if they weren't following what was happening
01:19
Maybe an OTC trade
P|
01:20
Paul N. | BAND (🅑) - I'll never DM you
Ok, PM me if you wanna buy some veo alright?
OK
01:20
O K
haha
P|
01:21
Paul N. | BAND (🅑) - I'll never DM you
would love to do it now 😍
MF
01:47
Mr Flintstone
buying veo 50% off
01:48
Because of fork probability
OK
01:48
O K
Interesting strategy
MF
01:50
Mr Flintstone
really it should be nearly 100% off if they have majority hash rate
OK
01:51
O K
Well, if they had majority hashrate, they'd have a longer chain
MF
01:51
Mr Flintstone
eventually
01:52
it seems like #1 priority for amoveo should be node stability right now
01:52
unless I am missing something
01:53
01:53
let me know if u agree
01:53
we can’t keep having situations where nodes ignore blocks from other nodes
I
01:54
Iridescence
It's hard to tell whether nodes intentionally or unintentionally ignore blocks
01:54
But I guess if we are confident that nodes don't unintentionally ignore blocks, then we can be sure when they are intentionally doing so
JM
P|
01:55
Paul N. | BAND (🅑) - I'll never DM you
let's have 5 more pools like this, and we're good
MF
P|
01:55
Paul N. | BAND (🅑) - I'll never DM you
and I'm just gonna stop mining
MF
01:55
Mr Flintstone
I do not think this is intentional, but you are right that we can’t know for sure
MH
01:56
Mandel Hoff
It's not possible to know, but it appears to have happened to two very independent nodes within a 30 hour time span. It seems like nodes are crashing in to this, and any node with 51% in that state will unintentionally "attack".
MF
01:57
Mr Flintstone
yeah, that is why I think it makes sense for the focus to be on fixing this issue
OK
01:59
O K
For one thing, I'm hodling veo
01:59
I've not sold any
02:00
I want the network to be stable and for veo to grow naturally
02:01
http://185.117.73.74/amoveo-network-status spread is getting wider
MH
02:02
Mandel Hoff
Fork started 25 blocks ago. Half-way if it has a 50 block max.
JM
02:03
J M
i think if you'd want to enforce node uptime and prevent ignoring blocks you'd have to punish ignoring blocks, intentionally or unintentionally, a la Proof of Stake
02:05
otherwise it's all reliant on good faith
OK
02:44
O K
Does anyone know which of Zack's nodes is the one he's using for mining?
S
02:44
Sy
I just resynced mine again
OK
02:45
O K
Welcome to the long chain
MF
02:46
Mr Flintstone
is the 50 block max a fork choice rule? I’m just a little confused how it exactly works
OK
02:47
O K
It's hard coded into the nodes
MF
02:50
Mr Flintstone
yeah, but it’s an additional fork choice rule in addition to “we will use the chain with most work”
02:51
?
IP
02:52
I P
does that unknown miner getting back on the chain or catching up?
Z
02:58
In reply to this message
No, it is in the configuration file. You can make it more or less, and you node works fine.
If it is bigger, then the memory requirements of running a full node is bigger.
If it is bigger, then the memory requirements of running a full node is bigger.
IP
MF
Z
02:58
Zack
Maybe they don't speak English.
IP
02:59
I P
i mean when there was a problem with amoveopool2 forking we could discuss it here
Z
02:59
Zack
Like when kassel wasn't watching the chat, because he mostly just spoke German
OK
IP
03:03
I P
ok if these guys don't speak english or don't communicate in any way
03:03
what do we do?
OK
03:04
O K
It's going to be interesting to see what happens in the next 20 blocks or so
Z
03:06
Zack
They seem frozen to me. Are you sure they are building a fork?
How could he get 11 blocks behind since he has so much more hash power?
How could he get 11 blocks behind since he has so much more hash power?
OK
03:07
O K
Yes, the spread has been widening, but they have been building
03:07
Or they may have recently frozen
03:07
But at least at one point, they were building
03:08
The split happened around 10780
Z
03:09
Zack
Are both sides frozen? No blocks for 17 minutes
03:13
there is another block from amoveopool2. we are not frozen.
OK
03:14
O K
That was a long one
MF
Z
03:17
Zack
In reply to this message
they got 30 blocks in a row at one point, so they were >50% then. Maybe not now.
03:17
they have been stuck at 806 so long, I think they are crashed.
MH
03:20
Mandel Hoff
They went +1
Z
03:22
Zack
so weird. why are 3 nodes on the fork? why are they mining so slowly?
OK
03:22
O K
Right? it's been really weird to watch it develop
03:22
for awhile we were 2-4 blocks away from each other, and it would fluctuate
S
03:23
Sy
"The Unknown Miner
"? 😂
"? 😂
MH
03:25
Mandel Hoff
About 10 blocks before the fork, there was another ~9 block fork that our nodes threw away and joined their fork.
J
03:26
Jim
Can you put a note out on Twitter, probably many people don’t read Telegram.
Z
03:26
Zack
A note saying what?
J
03:27
Jim
That whatever IP above is on a fork. Or wait until it resolves?
Z
03:28
Zack
Why would this be important for people to know?
J
03:29
Jim
IP
I P 23.03.2018 02:58:20
the problem is that these guys do not communicate in any way
Z
03:30
Zack
right, a twitter message to tell them tocontact us
J
03:30
Jim
Yeah, as I mentioned some people don’t read telegram
Z
OK
04:10
O K
Looks like their node went down
S
04:13
Sy
how fast is mandels miner with a 1070ti/1080?
J
04:14
Jim
Trying to look at channels on light wallet. Loaded a wallet file. Typed in amount to lock in (in Satoshis?), channel delay (0?) and duration (1000 blocks?), clicked make channel, nothing seemed to happen. Clicked save channel data to file, got s 2 byte file containing {}. I’m doing something wrong?
Z
04:15
Zack
In reply to this message
Yes. There is a minimum delay or else it won't work. I think 100 blocks.
This is how many blocks you have to stop your partner if they try closing at the wrong channel state.
This is how many blocks you have to stop your partner if they try closing at the wrong channel state.
OK
04:15
It's been awhile since that miner has been tweaked
04:18
And to be fair I haven't spent very much time at all playing with the variables
04:18
I think I use 96 168
Z
04:23
Zack
The optimal values probably changed when the POW algorithm changed
Z
04:42
Zack
30 minutes at the same blockheight
OK
04:43
O K
hmm
04:43
Unknown Miner is back
04:47
How long has he been back?
Z
04:48
Zack
more than 15 minutes I think
OK
04:48
O K
That's strange
Z
04:48
Zack
is your pool ok? why no blocks?
OK
04:48
O K
Everything seems ok, cards get work
04:48
I could reset the node
04:48
Let me give it a shot
Z
04:49
Zack
it isn't giving weird error messages?
04:49
it could be from randomness
OK
04:49
O K
quite a bit of talk_helper failed_connect
04:49
Let me screenshot
04:50
After the 17 min delay last time I reset the mining node, it had displayed some erorrs before, which it doesn't usually
04:50
this time it hasn't though
Z
04:51
Zack
you got a block. I guess it was randomness
OK
04:51
O K
Z
04:51
Zack
43 minutes.
Poisson distributions are like that
Poisson distributions are like that
04:52
trie died! that looks pretty serious. I think your consensus state must be corrupted.
OK
04:52
O K
I'll clean and restart
04:54
It's syncing now
04:55
Is this something I should make more use of? I tried it a couple times, but couldn't tell if it was doing anything
block_absorber:recover(quick).%only reads 90% of blocks, but is faster. what does it look like when it's working properly?
04:55
Usually I just re-download the blocks
Z
04:56
Zack
Im not sure if it is working right now. I think when you use it, it just ends up downloading the blocks normally.
04:57
it is supposed to read all the blocks from the hard drive, and then start syncing with the network to see if there are any more blocks after.
OK
05:05
O K
It's strange that TUM is not getting any blocks
05:07
Looks like you got one
05:07
Cool
MF
05:14
Mr Flintstone
shout out to randomness
OK
05:19
O K
Looks like he's full steam ahead again maybe
Z
05:21
Zack
yes, we are getting a good mix now
Z
05:58
Zack
and now TUM makes 8 blocks in 11 minutes.
haha
I wonder what they are thinking.
haha
I wonder what they are thinking.
MF
06:03
Mr Flintstone
nice
06:04
was it a known pubkey?
Z
06:04
Zack
my mistake, I was looking at the wrong oracle. It seems like no one made a bet.
MF
06:05
Mr Flintstone
haha. Looks like there is still a free lunch on the table!
Z
06:05
Zack
it shouldn't be possible to make oracle_bet txs right now anyway. there is no oracle in the betting phase.
MF
06:05
Mr Flintstone
oracle comes after what block?
Z
06:06
Zack
12000, that is when we will know the next difficulty.
it is over/under at 27 000 th/block
it is over/under at 27 000 th/block
06:06
we almost certainly wont increase in difficulty 50x necessary to reach this target.
MF
06:07
Mr Flintstone
yeah that’s why I think there is free money to be made
Z
06:07
Zack
oh yes, I am betting the wrong direction. you are right
MF
06:07
Mr Flintstone
can you help us understand exactly what the figure means after you hit “lookup market” on the light node?
06:08
The x axis represents a probability?
Z
06:08
Zack
the graph that is black and blue?
MF
06:08
Mr Flintstone
yeah
Z
06:08
Zack
probability and price are the same thing. they are the x-axis
06:08
the y-axis is the number of veo at stake
MF
06:08
Mr Flintstone
what does the y axis represent
Z
06:08
Zack
this is a market depth chart
MF
06:08
Mr Flintstone
so, there is 0.3 veo in total on the order book?
Z
MF
06:10
Mr Flintstone
users can market sell a total of 0.1 veo at a price of ~15%?
06:11
hmm I think I have been misinterpreting. I think I see what you mean by depth chart now
06:11
so there are no limit sell orders on the book? Only limit buy orders?
Z
06:11
Zack
I am betting about 0.2 at 1 to 3 odds.
So to match that entire bet, you could put up 0.6 veo at 3 to 1 odds.
So to match that entire bet, you could put up 0.6 veo at 3 to 1 odds.
06:11
there are limit orders in both directions.
06:12
oh, in the current moment there are only orders of "true" and no orders of "false".
MF
06:12
Mr Flintstone
I think maybe it would help with the abstraction if we saw an actual order book along with the depth chart
Z
06:12
Zack
you can buy "true" and you can sell "true". you can buy "false" and you can sell "false."
MF
06:12
Mr Flintstone
speaking only for myself though so others are free to chime in
Z
06:12
Zack
you can see your personal orders in the light wallet
06:13
yeah, an order book would be a cool upgrade
MF
06:13
Mr Flintstone
but you can’t see all of the available liquidity in an order book format just yet
Z
06:13
Zack
you can see all the liquidity
MF
06:13
Mr Flintstone
In reply to this message
I think it’s starfing to make more sense to me now, thanks
Z
06:13
Zack
the graph goes from 0 to 100, that is every possible price. so you see it all.
MF
06:14
Mr Flintstone
so, if I fill your order of true, that means I am taking the other side?
Z
06:14
Zack
I am betting on true, so if you bet on false, and our trades can match, then they will be matched.
06:14
you have to be willing to pay a high enough price for them to match
MF
06:14
Mr Flintstone
got it
06:16
There is 0.2 at 2:1 odds and 0.1 at like 5:1 odds?
06:17
(33% chance and 17% chance respectively)
Z
06:18
Zack
If you bet at price 0.2, then it is 1:4, a 20% chance of wining.
And if you bet at price 0.9, it is 9:1
A 90% chance of winning.
And if you bet at price 0.9, it is 9:1
A 90% chance of winning.
MF
06:19
Mr Flintstone
0.2 veo available to be bet against at 2:1 odds I mean, sorry
06:19
in this particular market
Z
06:19
Zack
Assuming the market is efficient
06:19
In reply to this message
Yeah, that is what is happening. So I miscalculated before. You only need 0.4 to bet against the 0.2.
06:20
At that price
MF
06:20
Mr Flintstone
very cool. Thank you for helping me to understand
06:20
I think I will make a bet against this tonight, unless anyone wants to front run me
06:20
at any rate, I think I’ll write a simple primer to help other people understand how to use and interpret these markets
Z
06:26
http://159.89.106.253:8080/explorer.html
Here, I moved it to the other server.
Here, I moved it to the other server.
MF
06:29
Mr Flintstone
In reply to this message
does it take time for the depth chart to show up accuratelyV
Z
06:29
Zack
I haven't made any bets yet, so if it empty, then it is working correctly.
MF
06:30
Mr Flintstone
oh makes sense
Z
06:30
Zack
I found a problem with closing my channel with the first server.
MF
06:30
Mr Flintstone
lol I assume you are going to make the odds less juicy
Z
06:30
Zack
I don't want to encourage people to make channels now, while it isn't possible to close them.
OK
06:31
O K
So, we have done 50x since block 4000 (roughly)
Z
06:31
Zack
great
OK
06:32
O K
This is whether we can do another close to 50x H/b in 1000 more blocks
Z
06:32
Zack
it averages out the entire 2000 block period, so even if we went 50x by the end, it wouldn't be enough.
OK
06:33
O K
Gotcha
Z
06:33
Zack
I think it is less than 1% chance we will reach this difficulty by block 12000
MF
OK
06:33
O K
If everyone bets one way, what is the benefit to betters?
MF
06:33
Mr Flintstone
In reply to this message
there has to be liquidity to make a bet that will pay out one way or the other
Z
06:34
Zack
In reply to this message
if your bet doesn't get matched, then you just get your money back regardless of the outcome.
OK
06:34
O K
👍
06:36
And once someone matches a bet, they may choose to unmatch the bet before the results are in?
Z
06:41
Zack
In reply to this message
no, once your bet is matched, then you have shares.
If you buy shares of the opposite type, then you can combine the 2 kinds of shares and change them into veo.
So if you buy shares of type 1 for price 0.6, and buy shares of type 2 for 0.5, then combine them. you lost about 9% of the money you spent.
If you buy shares of type 1 for price 0.1, and shares of 2 for price 0.4 and combine them, then you doubled your money.
If you buy shares of the opposite type, then you can combine the 2 kinds of shares and change them into veo.
So if you buy shares of type 1 for price 0.6, and buy shares of type 2 for 0.5, then combine them. you lost about 9% of the money you spent.
If you buy shares of type 1 for price 0.1, and shares of 2 for price 0.4 and combine them, then you doubled your money.
06:42
This is how derivatives trading works without blockchain too.
OK
06:42
O K
Thanks for the explanation. I think I've been confused because I asked about changing bets, and you said you could change the bet even after the event is passed. But I see now why that wasn't the right question to ask
Z
06:45
Zack
In reply to this message
you can buy and sell shares of either type, even after we know the outcome of the event.
06:45
Once we know the outcome, the price will go almost all the way into one direction.
06:46
so if you don't want to wait for the oracle to settle (which takes at least 1000 blocks), you can get your money out more quickly by buying shares of the opposite type
OK
06:46
O K
Cool
Z
06:48
Zack
We can probably reuse some documentation about betting from augur.
It is pretty complicated explaining unmatched bets vs shares.
It is pretty complicated explaining unmatched bets vs shares.
Z
07:39
Zack
I restarted the node, and now closing channels works correctly.
I added a print statment, so next time this happens we will know more about what is going on.
I added a print statment, so next time this happens we will know more about what is going on.
07:41
there are about 14500 veo now.
07:43
Zack This is the last 1000 line of crash.log when my node was crashed. Please use if it's helpful.
Z
07:44
Zack
Thank you catweed
I
13:43
Iridescence
Test
G
15:52
Gonzalo
Zack FYI: days ago I upgraded my VPS node to match my dedicated server node, both are now 4 cores / 4 gb. I confirm that the VPS node stills failing sometimes, but not the baremetal one:
eheap_alloc: Cannot allocate 1581921408 bytes of memory (of type "old_heap").
[End]
15:55
*update: dedicated server crashed as well, but this was the 1st time
15:57
TUM and amoveopool2 at the same height now... who won??
16:03
absorb block 10900
["channel","enI56BoniGEvcG0QLhUxgzxdRZ2ykkBkJH5oi16/3H0=","BCjdlkTKyFh7BBx4grLUGFJCedmzo4e0XT1KJtbSwq5vCJHrPltHATB+maZ+Pncjnfvt9CsCcI9Rn1vO+fPLIV4=","BPWNDtqS
xVx5z1LLHKf39ks6M0uRMIWYVIWd5PPgRofi+mB1xuPyplCYEPRwqLDHbdpFaKPhJ07IB+bGFqbGlfs=",50000000,49999999,0,1,9265,200,0]another get_blocks thread
absorb block 10910
Z
16:34
Zack
Yes, that is a channel I closed. I guess there is a print statement in the close channel tx.
G
16:57
Gonzalo
👍👍
P|
17:24
Paul N. | BAND (🅑) - I'll never DM you
So the next adjustment will be super expensive to mine a block right?
17:24
about 3x more expensive?
B
Z
B
17:39
Ben
ok, so no wallet/explorer?
17:40
@potat_o is the Wallet/send VEO via Pool intentionaly not working?
OK
17:41
O K
No, it's just a convenience tool, you can use another node's tools
B
17:42
Ben
currently not very convinient :)
B
17:42
17:42
hmmh
OK
17:46
I'll add the same disclaimer from the other two pages to the wallet page, thanks for pointing it out
B
17:47
Ben
yeah, btw. like your Pool good job so far.
OK
17:48
O K
Thank you :)
Z
17:56
The types of errors we get now are a little different from before.
It is still the case that the error is happening when the database is getting corrupted. Which means it must be related to the garbage collection or pruning of the consensus state.
It had been the case that mining nodes crashed more often, and nodes crashing at different heights. Now we crash in unison, and it doesn't matter if you are mining. But the lead miner crashes less frequently.
I think that the problems with garbage collection related to mining have been mostly fixed, and now we are dealing with some problem with pruning in relation to forks.
Something around here: https://github.com/zack-bitcoin/amoveo/blob/master/apps/amoveo_core/src/consensus/chain/recent_blocks.erl#L59
It is still the case that the error is happening when the database is getting corrupted. Which means it must be related to the garbage collection or pruning of the consensus state.
It had been the case that mining nodes crashed more often, and nodes crashing at different heights. Now we crash in unison, and it doesn't matter if you are mining. But the lead miner crashes less frequently.
I think that the problems with garbage collection related to mining have been mostly fixed, and now we are dealing with some problem with pruning in relation to forks.
Something around here: https://github.com/zack-bitcoin/amoveo/blob/master/apps/amoveo_core/src/consensus/chain/recent_blocks.erl#L59
18:04
I think I see a problem.
It seems like we are deleting the parents of blocks in this list. But if there is a fork, then 2 blocks will share a parent, so it attempts to delete the parent twice.
It seems like we are deleting the parents of blocks in this list. But if there is a fork, then 2 blocks will share a parent, so it attempts to delete the parent twice.
18:05
One way to fix this is to move the "remove_before" function from recent_blocks.erl to inside the tree_data gen_server.
19:56
Deleted Account
In reply to this message
when i use 159.89.106.253 wallet spend veo,on the page is ok,but my balance does not change
19:57
it last more than 5 min
20:01
Deleted Account
how about today? is that all block mined by unknown guy?
20:02
my 1080ti mined 0.1 veo yesterday.
Z
20:04
Zack
I programmed a fix, and updated my nodes. Hopefully they wont crash or cause 51% attacks any more.
20:06
In reply to this message
I don't understand.
The most recent block took more than 5 minutes, maybe that is related.
The most recent block took more than 5 minutes, maybe that is related.
Z
20:09
Zack
I turned
block_absorber:recover(quick). on again.
N
21:14
Deleted Account
Running into a small issue....4 of 5 of my cards are running fine, hashing like normal, one card everytime a share is found, it says difficulty too low, invalid share. Any ideas? All cards are setup the exact same.
OK
21:15
O K
That's what the random string is meant to solve
21:15
Do you have a different random string for each?
21:15
Deleted Account
yes
OK
21:15
O K
Hmm
21:16
For the sake of testing, put only the problem card on a new address for a moment
21:19
Deleted Account
Done
N
21:21
NM$L
why Pending Confirmation Payments not confirmed?
OK
21:22
O K
I'll chk
N
OK
21:33
O K
Check your wallet balance on a light wallet in a few blocks
S
21:59
Sy
hmm i forked, no error message in node tho
22:00
current height: 11284
Deleted joined group by link from Group
OK
23:05
I know this could probably be easily fudged, but would it make sense to put a node version number on the explorer.html for each node
23:05
You could even hide it in the same color, so it would require highlighting or something
Z
23:05
Zack
In reply to this message
Thanks for the heads up.
Maybe this is because I didn't resync that node after the software update, so maybe it had a corrupted database since before the update. I am resyncing now.
Maybe this is because I didn't resync that node after the software update, so maybe it had a corrupted database since before the update. I am resyncing now.
OK
23:05
O K
So people who don't communicate with us, we will know?
Z
23:06
Zack
is this version number for whenever I do a software update?
OK
23:06
O K
Yes, something along those lines
Z
23:06
Zack
Should it be the hash of the github commit that the node is using?
OK
23:06
O K
That's an interesting idea
Z
23:07
Zack
There is already a version number, but it is intended for stopping txs replay on different sides of consensus forks.
OK
23:08
O K
Okay
23:08
Would it be much trouble to add a time stamp to the explorer.html information for who found a block?
23:08
I find myself using the explorers a lot to see if people are on different forks
Z
23:08
Zack
timestamp would be easy. good idea
23:11
Deleted Account
@Mandelhoff is there any news on sub 1 VEO payments from old amoveopool, for some reason I thought they where done already.
Z
23:11
Zack
I think that turing on block_absorber:recover messed some things up. and it recovers a lot slower than downloading the blocks from a peer.
So I turned it off again.
So I turned it off again.
23:15
Deleted Account
In reply to this message
Than something went wrong with my 0.7ish VEO, half of it pre-batman mind you :) adress is seen as new BOLsg59UYx6bipXxyvhwYXvDN5w9aENg//QpRZVUz18KXYp5M0448KFZnwx/6oI91egD/dFlk1FlRysU6x2KdwY=
B
OK
23:15
O K
Resyncing now
B
23:15
Ben
ah ok
OK
23:15
O K
Thank you for the heads up
23:15
It was spamming found a block, potential block died
B
23:17
Ben
sounds strange
Z
23:19
Zack
I think block syncing is a lot slower since I fixed that race condition.
OK
23:22
O K
It's hard for me to tell
23:26
Deleted Account
amoveopool down?
OK
23:27
O K
Not anymore :)
23:27
I had to reset the node, it was acting up
23:28
Deleted Account
So it's all the way back up now?
23:28
Deleted Account
In reply to this message
He said he pay all he owned. I got 0.7 veo unpaid. But I think he did his best
OK
23:28
O K
My miners are working, all the way back up
23:29
Deleted Account
Yup looks like I'm back up
MF
23:36
Mr Flintstone
11 top height peers, this is the most I think I have seen
Z
23:37
Zack
I am feeling pretty excited about the recent race condition fix.
I think this will prevent the majority of crashes and forks that we had been experiencing.
I think this will prevent the majority of crashes and forks that we had been experiencing.
MF
OK
I
23:44
Iridescence
😂😂😂
23:44
Great selling point
23:45
Deleted Account
In reply to this message
Yes it seems to be gone. If transactions/veo are disappearing it begs the obvious question but I'll leave it to someone else to ask.
24 March 2018
MF
00:03
Mr Flintstone
In reply to this message
there is a chance that your unpaid balance was actually on a fork?
00:03
idk
Z
02:34
Zack
How much are people currently paying to mine Veo?
02:35
We decided $8 per day per gigahash at one point I think?
IP
02:47
I P
is it hard to put up a node? what specs on vps do i need?
Z
02:48
Zack
My node with 500 mb of RAM is doing fine. $5 a month.
02:48
I use a node with 4 gigs of ram and 2 cpu for the mining pool. Because it is expensive when that one crashes.
IP
02:48
I P
In reply to this message
where do they pay to mine veo this way? i use gpus on 3 my pcs (this is what happens when you love pc hardware and too lazy to sell old stuff) and i pay only electric bill
Z
IP
02:50
I P
In reply to this message
ok i have a vps from vultr with 1 gig of ram to run ellerium masternode, i could perhaps setup a node there. VPS is in japan so it should be good to have a node at that location
Z
02:50
Zack
Lately, both the nodes have had the same amount of up time. So I guess it doesn't make a difference any more
IP
02:50
I P
is there a guide to set up a node?
Z
02:50
Zack
Yes
02:50
Check out the pinned message.
IP
02:51
I P
thank you, will do it, we need more nodes on the network. Zencash has like 8000 nodes lol
Z
02:52
Zack
I disagree.
Having more nodes doesn't make a difference once we pass like 20.
Having more nodes doesn't make a difference once we pass like 20.
02:52
What is important is the marginal cost to launch one more node.
02:52
And for us it is a low cost.
OK
02:52
O K
ZenCash secure nodes serve different purposes
Z
IP
OK
02:53
O K
It's similar to dash, masternodes built on Zcash framework
02:53
perhaps, I don't know
IP
02:54
I P
they wanted to relay z-z transactions and IPFS through big network of nodes which in theory sounds great
02:55
right now you just put up a node, it gets some computational challenge and if it passes and has uptime you get paid a small amount.
OK
02:56
O K
In reply to this message
I'm getting substantially less with my same miner setup, to the point where it's getting more difficult to estimate
02:56
What variables do we know right now?
02:57
I have earned 2.25 since amoveopool2 when live, but I did have some short downtime, even if we assume that's a whole day of downtime
Z
02:57
Zack
We know how many hashes it takes on average to find a block reward. We know the block reward size.
02:57
So we just need to know how much it costs to do 1 gh/s for a day.
OK
02:58
O K
My hashrate is like 5.4 GH/s
Z
02:58
Zack
But you purchased hardware, right?
I am wondering about people who rent hardware at the current market price.
I am wondering about people who rent hardware at the current market price.
02:59
It is hard to estimate the daily cost of purchased hardware
OK
02:59
O K
I know, I'm just using my numbers to get how much hashrate = how much daily veo, instead of network numbers
02:59
I think the network numbers are accurate now, but before I just used my numbers
Z
03:00
Zack
You get 5.4 gh/s, and how muh did the chips cost? We can at least calculate the amount of time to recuperate your costs.
OK
Z
03:01
Zack
Cool, it was about $10 per day per gh/s
OK
03:01
O K
Oh god, I paid retail. The equipment I have was like $3000+ dollars
03:02
Deleted Account
I paid $27.36 for 24 hours worth of 6gh
Z
03:02
Zack
So you would need like 35 or 40 Veo to cover the cost.
03:03
It probably changed when the mining algorithm changed.
03:03
Deleted Account
Yeah
Z
03:05
Zack
So it cost something like $26 to mine a Veo now.
And if the difficulty goes up by 3x, it will be about $75 per Veo.
So it looks like we will survive the next retargeting, just barely.
And if the difficulty goes up by 3x, it will be about $75 per Veo.
So it looks like we will survive the next retargeting, just barely.
MF
03:09
Mr Flintstone
what does this have to do with survival?
I
03:09
Iridescence
Eight V100 on Amazon is $25 per hour, a V100 can probably get around 8 GH/s or so
03:10
A single V100 instance is $3 an hour
Z
03:10
Zack
If it costs more to mine than the value of a token, mining would stop
MF
03:10
Mr Flintstone
In reply to this message
Why do you think the market value of a token won’t change
Z
03:11
Zack
In reply to this message
By that calculation it is $0.30 per( gigahash per second )per day
MF
03:11
Mr Flintstone
miners will be more reluctant to provide liquidity to a purchaser unless the price is higher
IP
03:11
I P
In reply to this message
well right now there is no market value as there is no exchange=))
MF
03:11
Mr Flintstone
also, we know for certain that not every single miner is mining to sell immediately
IP
03:11
I P
so we are all going in just on pure enthusiasm
MF
03:12
Deleted Account
I rented a v100 on aws and it did about 6gh/s
OK
03:12
O K
I dunno IP, the OTC price has been surprisingly stable
MF
03:12
Mr Flintstone
from otc transactions
IP
Z
03:12
Zack
In reply to this message
So it is less then $2 to mine a Veo? I need to rent some of those.
OK
03:12
O K
I don't understand, how did we come up with 26-40 dollars before, and now $2
03:12
After difficulty adjustment
MF
03:13
Deleted Account
1 v100 when I rented it was 6gh/s
MF
Z
03:13
Zack
My math could be wrong
MF
03:13
Mr Flintstone
oh wow nvm then I don’t understand the disconnect
OK
03:13
O K
Mining is way harder,
MF
03:13
Mr Flintstone
oh yeah, I was just thinking from pow change perspective
03:14
yeah something doesn’t add up
Z
03:14
Zack
Oh, he said $3 per hour, and I read it as $3 per day. So that estimate was off by a factor of 24.
03:15
It is like $50 per Veo with a v100
S
03:15
Sy
and yet ppl pay 80$....why bother calculating cost per gh?
Z
03:15
Zack
In reply to this message
Paying $80 makes sense since you don't have to deal with installing the miner
S
03:16
Sy
true 😂
OK
03:16
O K
I'm going to say I got 2.5 veo in 5 days (this is not quite accurate), that is 0.5 veo per day with 5.4GH/s ... Meaning 8 GH/s (by Iri's numbers) gets 0.75 Veo per day (one V100) which would cost what?
03:17
One V100 for one day
Z
03:17
Zack
$72 per day for a v100 they said
03:17
Same as $3 per hour
MF
Z
03:17
Zack
So about $100 per Veo by OKS estimate
OK
03:18
O K
Which is amateur hour
03:18
So, people ca ndo much better than me
MF
03:18
Mr Flintstone
lol
OK
03:18
O K
But it's a high side number
MF
03:18
Mr Flintstone
call it 50-100 usd to mine 1 veo per day depending on skill? from renting hardware
OK
03:18
O K
Sounds good
Z
03:18
Zack
It sounds like the best miners are paying about $26 per Veo.
OK
03:19
O K
Cool
03:22
Going the other way just for fun... 556 TH/b
03:22
One V100 needs to mine for 69500 seconds ?
I
Z
IP
03:23
I P
guys could you please help me sync my node
OK
03:23
O K
Of course IP
IP
03:23
I P
amoveo@guest:~/amoveo$ make prod-attach
Attaching to /tmp/erl_pipes/amoveo_core_prod@guest/erlang.pipe.1 (^D to exit)
Attaching to /tmp/erl_pipes/amoveo_core_prod@guest/erlang.pipe.1 (^D to exit)
03:23
i went there
Z
IP
03:24
I P
ok thx
OK
03:25
O K
19.3 hours
03:26
1.24 Veo per day
Z
03:27
Zack
For $72 per day.
So about $57.6 per Veo by that estimate
So about $57.6 per Veo by that estimate
OK
03:27
O K
Great
03:27
The 20s seems a bit low, that would mean they are either getting much better prices for rented power, or they have much better miners
Z
03:27
Zack
Only one person claimed to get that hashrate
03:28
Maybe they misestimated or something
OK
03:28
O K
Oh I see
Z
03:28
Zack
So $50-100 seems a reasonable range that people could be paying per Veo now
I
03:29
Iridescence
My 1080 at around 2.5 GH/s gets about 0.1 - 0.2 VEO per day
03:30
Kind of disheartening when a few weeks ago it was 1-2 VEO a day
03:30
But I guess that's competition
OK
03:30
O K
Haha yeah
03:30
It's still a better deal when you think about what mining ETH is like
IP
03:31
I P
mining btc and eth nowadays is a joke
Z
03:31
Zack
Once the profit margin of mining is small enough, then we can start considering increasing the block reward.
MF
03:36
Mr Flintstone
In reply to this message
most miners right now are not mining for short term profit
03:37
if they were, there would be much more otc liquidity at a lower price than the market value right now
OK
03:37
O K
It will be fun to play in more realistic markets on future hashrate
Z
03:38
Zack
Can you choose the hashrate to gamble on this time? My guess was so bad last time
OK
03:38
O K
The first market guess was good wasn't it?
03:39
I'm trying to find the new market now
Z
03:39
Zack
They both used the same oracle.
03:39
It's my 253 Explorer
OK
Z
03:40
Zack
Correct
MF
03:40
Mr Flintstone
In reply to this message
this is block 14000 diff as measured by hash per block?
Z
03:40
Zack
Yes
MF
03:40
Mr Flintstone
I feel like 4500 is reasonable
03:41
Th
Z
03:41
Zack
So you think it will go up about 3x in both retargeting events
MF
03:42
Mr Flintstone
current estimation per Jim’s stats page is 1500 th
03:42
so yeah, then another 3x would be vase case at least in my view
03:42
base case *
Z
03:42
Zack
Sounds like a reasonable guess to me
03:43
Maybe I should launch 3 markets, for 3 different prices.
OK
03:43
O K
The more the merrier
MF
03:43
Mr Flintstone
that would be interesting
03:44
as an aside, how have people’s nodes been doing since zack pushed the fixed earlier today?
OK
03:44
O K
Mine have been pretty happy, but I need 24 hours to say for sure
Z
03:44
Zack
My node crashed once, but I think it was because I didn't resync that node after updating. It was corrupted before I did the update.
03:45
The block period is up to 5 minutes now. Nodes don't crash much at this rate anyway.
MF
03:46
Mr Flintstone
yeah, I wonder what happened to the hash rate we had earlier
OK
03:48
O K
Seems like TUM's hashrate comes and goes
03:48
Even when their node is in sync
Z
03:50
Zack
Maybe there was a power outage where their miners are
03:51
Maybe they realized that raising the difficulty too much is a bad idea.
MF
03:53
Mr Flintstone
maybe they want to go nuts at 12k
03:53
we will see
I
03:53
Iridescence
But it'll be harder
Z
03:54
Zack
Maybe some other gpu minable cryptocurrency got more profitable to mine
03:54
Deleted Account
I have yet to find one lol
MF
03:54
Mr Flintstone
I do not think there is any strong concept of profitability here yet
03:55
unless there is way more otc activity than I am aware of
03:55
but I am usually plugged into these things given that I accumulate veo by purchasing rather than mining
I
04:03
Iridescence
What is OTC price currently?
Z
04:04
Zack
It might be the case that people who are posting trades are doing so just to manipulate the price
MF
04:07
Mr Flintstone
I would say fair market value was like 65-85 usd before this new miner showed up
04:07
I’d think it would be a little higher now
05:11
Deleted Account
I'm holding out for $100 per coin or higher :)
IP
05:12
I P
(amoveo_core_prod@guest)7> server crashed.
is this really bad, right?
is this really bad, right?
05:14
well, restarted and resyncing... hope it will work on the 3rd time=))
Z
IP
05:16
I P
less than 1 hour ago
MF
Z
05:17
Zack
What makes you think it "crashed"?
05:19
In reply to this message
This is an example of a poor error report.
It does not give me enough information to re-create the bug on my computer.
It does not give me enough information to re-create the bug on my computer.
MF
05:25
?*
IP
05:25
I P
well if there is a log i am willing to provide it
Z
IP
05:26
I P
well i thought that 'server crashed.' means it crashed=))
05:27
well right now my node is on 11417, other nodes +1 block so looks like it did not crash after all
Z
05:29
If you send an http request to a server, and that server fails to respond, then that message gets printed.
Erlang is a fail-fast language, so this is supposed to happen a lot.
If something goes wrong, it immediately crashes instead of wasting time doing invalid computations.
Erlang is a fail-fast language, so this is supposed to happen a lot.
If something goes wrong, it immediately crashes instead of wasting time doing invalid computations.
IP
05:34
I P
(amoveo_core_prod@guest)10> api:height().
11417
but in network stats i see recent block 11420
damn
11417
but in network stats i see recent block 11420
damn
05:34
node itself works http://45.77.8.119:8080/wallet.html
Z
05:35
Zack
did you do
sync_mode:normal().?
IP
05:35
I P
yes!
Z
05:38
Zack
It looks like you aren't appearing in the list of peers.
05:38
I guess when you restarted everyone added you to the blacklist, because they couldn't connect to you.
05:39
ill add you manually and see if that fixes it.
IP
05:40
I P
thank you! what should i do from my end?
Z
05:41
Zack
nothing.
05:43
looks like you are synced now @kitty123
IP
MF
Z
IP
06:18
I P
wow guys i've checked and actually got my first payout from pool, yay. i have 1 veo now, cool. At least something positive here
06:18
lost a lot of money trading bitcoin which moves like a drunken sailor
J
06:26
Jim
In reply to this message
Can happen, google sheets wasn’t designed for this so the data occasionally craps out
06:26
Planning to move to highcharts when I get the time
06:27
But I’ll have to rewrite the calculations to happen in javascript
06:27
For now, just refresh and wait if it doesn’t work
OK
06:42
O K
Guys it looks like there is someone mining to amoveopool2.com with bad parameters. You have, probably the GPU # configured before your address. I can't identify you and I can't pay you. You've got to fix your settings.
Z
06:43
Zack
One of my nodes crashed. The database was corrupted.
OK
06:43
O K
In reply to this message
You may have about 3GH/s and may be using Google cloud to mine with.
07:04
Deleted Account
amoveopool2 down?
07:04
Deleted Account
Appears so to me
07:04
503 error
OK
07:04
O K
On it
07:05
Deleted Account
👍
07:09
and we're back
07:09
at least the front end
OK
07:09
O K
Cards getting work
07:10
Should be good
07:10
Deleted Account
Yup just confirmed on my end
07:20
Deleted Account
thanks!
SS
09:13
Deleted Account
Sticker
Not included, change data exporting settings to download.
😉, 36.1 KB
09:13
what's the hashrate of GTX TITAN
I
09:14
Iridescence
TITAN V?
09:14
Deleted Account
yes
I
09:14
Iridescence
it's roughly the same class as the V100
09:14
but weaker
09:14
so I would guess around 5-6 GH/s
P|
10:45
Paul N. | BAND (🅑) - I'll never DM you
In reply to this message
($3 an hour * 24 hr/day) / (8 GH/s) = $9 per GH/s per day
10:49
In reply to this message
Why do we need more block reward in that scenario? If it gets more expensive to mine, miner will just sell Veo at higher price.
J
10:50
Jim
Woah, whoever tipped me on my stats page, thank you!
IP
10:52
I P
In reply to this message
well=) you need people to buy at higher price for you to sell. For example i want to sell btc at 20k =) any buyers?
P|
10:57
Paul N. | BAND (🅑) - I'll never DM you
Increasing block reward doesn't help -- that's my point. The only purpose that it serves is creating inflation. Mild inflation is good for nudging people to spend their coins, but at this point there is no pratical use of Veo in any way that economically benefits them yet. It allows late-comers to make more money -- that's all inflation will do right now.
IP
11:04
I P
In reply to this message
well idea is not to inflate it to heavens or hell. Mild inflation is good. The whole thing with early adopters is what pisses me off in crypto. Literally some guy mined bitcoins for fun and now he is stupidly rich whale and can manipulate market with his friends. Is this good or fair? No, not really. If people come later does not mean that these people are worse and deserve less reward. For sure there should be a balance.
MF
11:11
Mr Flintstone
whatever happens happens
11:11
not about fair or unfair
11:12
my guess is people are greedy and do not want the inflation rate to do anything but be positive yet monotonically decreasing which is consistent with an unchanged block reward
Z
11:14
Zack
my guess is that people are greedy, so they want the price to go up, which means they want Amoveo to be useful.
Amoveo is for markets, so it is as useful as the market cap is big. So this means they want a big market cap. Therefore, I am expecting most token holders to want the block reward to be increasing over time.
Amoveo is for markets, so it is as useful as the market cap is big. So this means they want a big market cap. Therefore, I am expecting most token holders to want the block reward to be increasing over time.
MF
11:15
Mr Flintstone
the market will optimize the price for any usage that participants demand
11:16
the market relative to the exchange rate of amoveo
11:16
not betting markets
Z
11:17
Zack
In reply to this message
the market cap and the growth rate are 2 different things that should be optimized separately.
No reason to artificially force them to move together. If you connect them this way, then only one can be optimized.
No reason to artificially force them to move together. If you connect them this way, then only one can be optimized.
MF
11:18
Mr Flintstone
if the market cap is not big enough to support the economic activity participants demand, the price of amoveo will rise and with it the market cap
Z
IP
11:21
I P
In reply to this message
this is so true. i'm looking forward that time when the network is big and stable, user experience is fluid and real life application is starting. that would be so awesome if i could see that come true
MF
11:25
Mr Flintstone
I guess we will find out what will happen
12:52
Deleted Account
increase block reward is a bad idea.
12:53
that make early mined veo useless.
M
12:54
Marc
is there a problem with amopool2 payouts. i think i am missing a payout of 1 veo. it was show as "Wallet Balance" but was deducted after a while.
12:55
Deleted Account
i just bought another 1080ti
M
12:56
Marc
i was making records of my balance hourly. please check.
13:03
i had this problem with my own pool (balance showing up but being deducted after some time).
M
14:19
Marc
much confuse. maybe i am at fault? idk. i will take a nap now.
N
16:12
NM$L
what price now？
IP
S
16:20
Sy
Higher
N
16:20
NM$L
sell some veo pm me with your best price
B
20:08
BG5EHI
sell some veo pm me
OK
N
OK
20:54
O K
In reply to this message
Hey Jamhan, it's at 12000 right? Zack could probably answer the mechanics of it better than I can
N
Z
21:15
Zack
yes. difficulty adjusts every 2000 blocks. so the next one is at 12000.
N
Z
21:22
Zack
In reply to this message
It takes the median of the first 1000 blockstamps N1, and the median of the next 1000 blockstamps N2.
estimated blocktime = (N2 - N1)/1000
New difficulty = Old difficulty * (target blocktime) / (estimated blocktime)
estimated blocktime = (N2 - N1)/1000
New difficulty = Old difficulty * (target blocktime) / (estimated blocktime)
21:26
Deleted Account
any develop updates beside mining ?
Z
21:26
Zack
the commits on github are all open source.
21:33
Deleted Account
Finally looked at the crash error I was getting it says unspecified launch, any ideas what that might mean
Z
OK
21:35
O K
I didn't get that error last night DS
21:35
I lowered some params and still used afterburner
21:36
My hashrate was significantly down though
21:36
I think a timed killall and reset with higher params is a good option
21:37
I reduced suffix to 10k
OK
21:37
O K
I didn't change suffix
21:37
Deleted Account
No afterburner
21:37
I'm thinking I'm going to try to do a scheduled killall what are you using task scheduler?
OK
21:38
O K
I haven't taken the time to figure it out yet but probably could be done in a batch script? Not very familiar with windows
21:40
have an infinite loop that runs each cmd on a 3 hour timer or something, would get the job done. I'll look into it this afternoon if I have time. Busy day ahead
21:41
Deleted Account
Yeah going to try to figure out something, even if I set all cmd Windows to close hourly and relaunch
OK
21:41
O K
Lowering my numblocks is what prevented crash
21:41
Deleted Account
Hmm
OK
21:42
O K
But significant decrease in hash, not worth it if we can get a script resetting
21:42
Deleted Account
Exactly
21:42
I'll see what I can come up with here in a bit, just woke up lol
J
23:16
Jim
In reply to this message
BTW my node for stats stayed in sync for a whole day with no user intervention. Good job.
Z
OK
23:17
O K
I'm also feeling good about it, great work Zack 👍
Z
23:22
Zack
It looks like one of my nodes died though.
The 253 one that has less ram seems to crash about once a day. But the one I run with he mining pool went 2 days without crashing.
The 253 one that has less ram seems to crash about once a day. But the one I run with he mining pool went 2 days without crashing.
MF
23:52
Mr Flintstone
great news about the node stability
23:53
I think we definitely want people to be able to run nodes if they only have like 500mb ram though right?
25 March 2018
S
00:01
Sy
Stability is more important than ram usage for now
MF
00:06
Mr Flintstone
yeah, I just mean in general tho
00:06
not like it needs to be prioritized
00:21
Deleted Account
@potat_o I was able to make a kill task command for the miners (I had to create a different instances of the gpu miner software for each miner) and installed a software to monitor for crashes and auto restart the miners, and scheduled the task for every hour
OK
00:22
O K
Nice work!
00:22
Deleted Account
Thanks I'll try to send you the video of it
Z
03:44
Zack
In reply to this message
It isn't crashing because it runs out of ram.
It is crashing because the cpu is slower, so race conditions happen more frequently.
Amoveo uses very little ram.
The limit is something like 280 mb, and actual usage stays below 100 mb.
It is crashing because the cpu is slower, so race conditions happen more frequently.
Amoveo uses very little ram.
The limit is something like 280 mb, and actual usage stays below 100 mb.
03:49
My mining node crashed.
I guess there is still another race condition for the database somewhere.
I guess there is still another race condition for the database somewhere.
OK
Z
04:10
Zack
15600 veo so far
04:11
Deleted Account
zack and ok 's pool both down?
OK
04:11
O K
Mine down for a few minutes, resyncing node
04:12
Back up shortly
Z
04:12
Zack
Mine is up
J
04:15
Jim
Is there an API command to get total amt of veo? Would like to display that
Z
04:15
Zack
there is an api command to get blocks by height. Each block has written on it the market cap.
04:16
It is the 16th element in the block-tuple
J
04:17
Jim
Hm, could work with that. Will need a sheet to store prev values though so don’t do too many lookups.
Z
04:20
Zack
This is much less expensive than the api for looking up all the hashrates at each block
OK
04:23
O K
We're back online
04:40
Deleted Account
We have made a new Amoveo Pool if anyone is interested. More info can be found on the Amoveo subreddit: https://www.reddit.com/r/Amoveo/comments/86vt5w/introducing_a_new_amoveo_pool/
OK
04:51
O K
Congrats Ivar!
IP
04:51
I P
In reply to this message
hey, that's great. would be cool if you tell us why your pool is better if it is better=)
G
04:56
Greg
Nice work!
Z
04:56
Zack
I put all three mining pools into the readme
Z
05:40
Zack
I found another way that the database is getting corrupted.
Last time I fixed it so now the database can correctly handle forks that are 1 block long, but we are still corrupting the database if a fork is more than 1 block long.
A temporary solution would be to stop garbage collecting any orphan blocks.
This will be a memory leak, but if you resync the blocks, you can recover the lost memory.
It isn't perfect, but it is a lot better than what we are doing now, and it means we can sync faster.
Last time I fixed it so now the database can correctly handle forks that are 1 block long, but we are still corrupting the database if a fork is more than 1 block long.
A temporary solution would be to stop garbage collecting any orphan blocks.
This will be a memory leak, but if you resync the blocks, you can recover the lost memory.
It isn't perfect, but it is a lot better than what we are doing now, and it means we can sync faster.
IP
05:47
Deleted Account
Thanks guys, we hope this will be a good contribution for Amoveo. We used to mine on amoveopool in the beginning of Amoveo, and our impression was that the hashrate estimate could be improved, and we feel like we reached our goal. We also share the same fee rate of amoveopool2 which would make it competitive. The most important factor would still be to further decentralizing the currency in order to stabilize it and make attacks harder to achieve.
IP
05:48
I P
In reply to this message
good luck with this new pool!! do you use VPS or dedicated server to run it?
Z
Deleted joined group by link from Group
06:52
Deleted Account
HI guys
06:52
is this the official amoveo telegram group?
06:52
A friend told me about this project and i am looking how to mine it right now , i am on windows and didnt make it yet
G
06:53
Gonzalo
Yes, are you the real whalepanda?
06:53
Deleted Account
you follow me on twitter?
G
06:53
Gonzalo
I follow the real one, yes 😜
06:54
Deleted Account
One friend that knows his shit told me to keep an eye in this project
06:54
So I decided to check on it
G
06:54
Gonzalo
Ok, welcome anyway
I
06:54
Iridescence
Who is whalepanda
06:55
Deleted Account
A panda that has some btc that is all
G
I
06:55
Iridescence
🐋🐼
06:56
Deleted Account
Do I mine this with cpu or i can use gpu as well?
M
06:57
Marc
gpu
G
06:58
Gonzalo
Cpu was profitable only for the first hours
06:59
Deleted Account
Thanks guys , will try to mine , for now no other way to buy amoveo?
OK
06:59
O K
The discord seems to be the most active market, but there is reddit.com/r/amoveotrader too
06:59
Only OTC right now, Zack the developer is willing to do escrow services
I
07:00
Iridescence
What was the estimated cost per VEO to mine?
07:00
I forget
07:00
Like 50-80 per VEO?
07:00
Deleted Account
Would be easier for me if could directly trade , great
OK
07:00
O K
Yes Iri
07:00
Something like that
07:00
With rented hardware
07:08
Deleted Account
In reply to this message
Hi! There is a block explorer available here http://amoveo.noncense.tech:4444/explorer.html
Z
IP
07:12
I P
In reply to this message
or if you are rich you could hire someone to mine veo for you with amazon rental gpus for a fee
07:33
Deleted Account
In reply to this message
Sorry missed your question! The pool software is running on a 6 core VPS, written from the ground up in Elixir/Erlang
IP
07:34
I P
nice
I
Z
07:55
Zack
I think the first step for atomic swapping is to launch a testnet, and to atomic swap Veo for testnet-Veo.
08:06
Deleted Account
glad to have a new pool. I added description to network stats page.
http://185.117.73.74/amoveo-network-status
http://185.117.73.74/amoveo-network-status
IP
08:11
like IP node or smth=)
08:18
Deleted Account
In reply to this message
It will not be as the old official C miner is still using the pre block 9000 hashing as can be seen here https://github.com/zack-bitcoin/amoveo-c-miner/blob/master/amoveo_pow.c#L59-L65
08:20
If you want to mine using CPU (should be mostly for educational purposes) you can use this one: https://github.com/Mandelhoff/AmoveoMinerCpu
Z
08:20
Zack
I pushed the upgrade to github for the software for the full node to fix how forks are handled. hopefully this prevents the database from getting corrupted so it wont crash so often any more.
This causes a small data leak, which will consume around (txs per block) * (200 bytes) of ram every time there is an orphaned block.
But when you resync the blocks, all the orphans are ignored. so this ram is recovered.
This causes a small data leak, which will consume around (txs per block) * (200 bytes) of ram every time there is an orphaned block.
But when you resync the blocks, all the orphans are ignored. so this ram is recovered.
08:20
In reply to this message
you can use the
partial-hash-fix branch of the code for mining after block 9000.
08:21
Deleted Account
Ah sorry didn't know, that's great Zack!
Z
08:30
Zack
Everyone else is using a 2% fee for their mining pools, so I lowered my fee from 3% to 2%.
08:32
Deleted Account
Pulled the node update. My node runs on very cheap VPS, so I hope this fix would help.
Thank you Zack.
Thank you Zack.
Z
OK
11:30
O K
Syncs fast 40 blocks at a time then long lag, can't tell if it's faster
12:06
Deleted Account
just bought a 1080ti but it can only get 2gh/s
12:06
is that PCIE 1x to 16x line make it slow?
IP
12:14
I P
In reply to this message
no, probably you need to tune miner parameters, downclock memory, overclock core
12:15
i get 1.6ghs with 1070 both on x16 slot and on riser x16-x1 card
S
12:51
Sy
Nice...mining cards
S
13:07
Sy
on windows, easy - get msi afterburner
13:07
on linux, more tricky
13:22
1080ti
S
13:25
Sy
worth it if you are in a tight spot
14:48
Deleted Account
In reply to this message
make sure you have a good cpu and decent ram. also right parameters. you should get far more. i get 3.1
IP
15:00
don't ask me why on earth would someone build such a combo
15:00
Deleted Account
core 2
15:00
sounds familiar
15:00
from long back
15:00
forgotten history
IP
15:00
I P
10 years long back lol
15:01
Deleted Account
phew
15:01
i used to play aoe with that kind of config
AS
15:09
Aizen Sou
In reply to this message
Holy shit the real whalepanda is here? Anyway to verify that it's the real you, dude ?
IP
15:11
Deleted Account
yeah thats him, saw him in nimiq telegram sometime back
16:03
i saw the block reward up to .98
Z
17:14
Zack
The fee is 2% now. Correct.
M
17:45
Minieep21
WhalePanda on twitter says he never heard of Amoveo
AS
17:48
Aizen Sou
Yeah probably fake WhalePanda
IP
17:50
I P
i like how in twitter every important person has [not giving away crypto]
G
M
G
AS
IP
Z
19:40
Zack
I want to buy Veo. Will anyone sell for $50?
19:44
A family member of mine gave me some money and told me to buy Veo for them.
IP
Z
20:36
Deleted Account
Someone just attempted to mine on the Noncense pool with their miner not running in "pool mode" so we received no public key in the mining_data request. We won't send work to these miners as we have no way of paying you for your work. If you are reading this, please let me know if you need some mining assitance
Z
20:57
Zack
In reply to this message
As long as they send a pubkey with the work, you should still be able to pay them. My pool would still pay them.
21:04
Deleted Account
In reply to this message
That won't work for this pool and (I think) it won't work for AmoveoPool2 either. We require a public key on the work request in order to send the appropriate share difficulty back along with the work to get shares submitted evenly across all miners
MF
21:42
let us know if you have success at this price point
Z
21:43
Zack
In reply to this message
Yes. I'll let you know.
I don't trust the anonymous trade messages on the forums.
No offers yet.
I don't trust the anonymous trade messages on the forums.
No offers yet.
MF
21:43
Mr Flintstone
you can trust me more though I think
21:43
maybe you disagree
N
21:44
NM$L
I could sell you but not this price.
Z
OK
21:45
O K
Last night I reported new node would download 40 blcoks and lag heavily at a time, I didn't know if it was faster
21:45
Today I resynced and man
21:45
Blazing fast
MF
21:45
Mr Flintstone
there are certain things that need to be trust minimized and certain things that do not need to be
Z
N
21:58
you know the mining cost, 50$ is so stingy
EW
MF
22:00
Mr Flintstone
aws rental was like 50-80usd per veo?
N
22:02
It's around 8$ per GH/s per day
22:04
12000 block is coming soon
OK
22:06
O K
Zack catweed 45.77.196.69 is going to be an amoveopool2.com node ... It's just a reference node for now
22:07
It lost sync overnight, probably just not recognized by some of the network so got the short end of the headers stick 🤷♀️
Z
22:11
Zack
In reply to this message
Did you update recently? The fix yesterday might be a big improvement.
OK
22:12
O K
Yes, I git pull this morning to re-sync, no changes
22:12
I only set it up last night
22:12
It just sort of fell behind, not a crash like has happened with a very active node
Z
22:15
Zack
I guess the software still isn't perfect
22:16
But I think we will at least have a significant reduction in crashes.
OK
22:16
O K
I wasn't trying to complain, I was just letting you know about the IP really
22:16
Things have been trending better for sure 👍
Z
22:19
Zack
7 blocks till retarget
OK
22:31
O K
12000
N
22:33
NM$L
great
22:38
when 12001
Z
22:42
Zack
We made it to 12001.
OK
22:43
O K
not bad!
N
22:43
NM$L
nice
Z
22:43
Zack
Difficulty went up almost 4x
OK
22:43
O K
In 1 week we will be back under 10 minutes
22:43
Whatever math that is, I would make that bet (make it 1.5 weeks)
N
22:43
NM$L
AS
22:44
Aizen Sou
4x diff ? Shit. Now it should be 300$ per coin at least
Z
22:44
Zack
Gigahash per second won't be accurate for 20 more blocks
N
P|
22:48
Paul N. | BAND (🅑) - I'll never DM you
With $300/veo and 52,596 veo mined/year, that makes the projected marketcap after 2 year of mining to be 31.5 million USD
AS
22:51
Aizen Sou
Still too little. Bismuth got pumped to 50mil$ while inferior to Amoveo in many ways.
OK
22:52
O K
Pumping is not the way, it will grow organically
Z
22:52
Zack
In reply to this message
My previous projects got up to 1/2 billion each, and we show more promise than them.
Once the lightning markets have a few hundred regular users, then I expect the market cap projected 2 years out will be over a billion.
Once the lightning markets have a few hundred regular users, then I expect the market cap projected 2 years out will be over a billion.
Z
22:53
Deleted Account
I only get two 1080ti
22:53
I definitely won't buy in more cards
22:54
is there possibility that difficulty become lower?
Z
22:54
Zack
In reply to this message
No, but we could raise the block reward. Which is almost the same thing.
MF
22:55
Mr Flintstone
Wow diff 2k.
22:55
Deleted Account
endless rising difficulty make people like us quit mining. Probably one day only kassel and batman mininh
P|
22:56
Paul N. | BAND (🅑) - I'll never DM you
In reply to this message
Oof course, this is the projected valuation based on USD spent on mining alone, and not including utilities and speculative factor. If the blockreward remains, we should see $10k/veo.
MF
P|
22:57
Paul N. | BAND (🅑) - I'll never DM you
In reply to this message
That's how it works. The margin from mining should be very low and only people who can mine efficiently can sustain. Same thing with every chain.
N
22:57
NM$L
if under 100$, nobody want to mine.
22:57
at this diff
Z
MF
22:57
Mr Flintstone
who is gonna sell for under 100 usd right now?
22:57
I feel like it won’t happen
22:57
could be wrong tho
Z
22:58
Zack
I should have bought more 2 weeks ago ;_;
MF
22:58
Mr Flintstone
Zack you are gonna get paid to a sufficient degree with the dev reward
P|
MF
22:58
Mr Flintstone
and it is in veo
N
P|
22:59
Paul N. | BAND (🅑) - I'll never DM you
But you got the dev rewards man. 🤑
Z
22:59
Zack
I think it was like $2 per Veo at one point?
MF
23:00
Mr Flintstone
the lowest I ever saw for otc was 24
N
23:00
NM$L
How about raise block reward?
MF
23:00
Mr Flintstone
I got here on day 2 tho
P|
23:00
Paul N. | BAND (🅑) - I'll never DM you
I miss the CPU mining days
23:00
Deleted Account
the first day i am in.
23:01
and i only get 5 veo now
P|
23:01
Paul N. | BAND (🅑) - I'll never DM you
why didn't I use more than 100 cores to mine 😂
23:01
Deleted Account
should buy GPU more earlier
N
23:11
NM$L
when Cryptopia
M
23:12
Minieep21
when Bitfinex
MF
23:12
Mr Flintstone
lol
23:12
4 real tho we should wait a while before exchange listing
23:13
idk at least until things are very stable
AS
MF
23:20
this is my Dream
JS
23:20
Jon Snow
When Coinbase
N
23:27
NM$L
Augur,Aeternity
B
23:58
Ben
selling 50 @200$
26 March 2018
S
00:26
Sy
It will take a few days for the price to adjust the least
00:26
Ppl still own their easier coind
MF
00:33
Mr Flintstone
yeah
00:34
but the 4x was a surprise relative to the 3x expectation
00:34
so price should increase a little initially
G
J
00:40
Jim
Hm, so I guessed it more accurately this time, but still off. Guesses should be better as hash rate stabilize and we stop doing 3-5x each time
00:41
And yeah, DIV/0 is cause we have no data until 10 blocks
G
01:07
Deleted Account
So with the difficulty is the new price more like 175-200 each?
S
01:11
Sy
sooner or later, yeah
Deleted joined group by link from Group
Z
01:22
Zack
In reply to this message
It takes the median of the first 1000 n1, and he median of the second 1000 n2.
Then computes.
X = (N2 -n1) / 1000.
New difficulty = (old difficulty) *(600 seconds)/(x)
Then computes.
X = (N2 -n1) / 1000.
New difficulty = (old difficulty) *(600 seconds)/(x)
IP
01:29
I P
In reply to this message
well if you did not notice on whattomine profit from mining zcash and ethereum is very little right now. So even at price 100$ and diff going up amoveo is still more profitable to mine. Maybe it is not that profitable to rent gpus from amazon cloud to mine after diff went up 4x- that could be true, though it needs to get assessed. But if you own your gpus you should not get huge profit on them anyways
OK
01:32
O K
Yes. exactly IP, there are a lot of miners with infrastructure, not renting and the amoveo reward is still very high compared to big name coins
IP
N
P|
01:37
Paul N. | BAND (🅑) - I'll never DM you
anyone know the current txn fee of veo right now?
N
01:37
NM$L
aws hash power will gone
Z
IP
01:41
I P
In reply to this message
i guess we will be able to adjust fees once a more easy to use wallet gets released, right?
Z
01:43
Zack
In reply to this message
The wallet is programmed to pay as little fee as possible, because there is no backlog of zeroth confirmation txs.
IP
01:43
I P
ah, ok, i see, to prevent network spam, right?
Boob Grabber joined group by link from Group
J
JS
02:36
Jon Snow
11 blocks in the past 4 hours, since 12000 block
I
02:36
Iridescence
Haha
N
02:37
NM$L
why only 11
I
02:37
Iridescence
So on average 2.5 blocks per hour
Z
02:52
Zack
looks like blocks are averaging at about 20 minutes each.
Before the adjustment we were taking about 4 or 5 minutes per block, so I think no many miners have shut off. We are looking good so far.
Before the adjustment we were taking about 4 or 5 minutes per block, so I think no many miners have shut off. We are looking good so far.
OK
02:53
O K
👍
J
02:53
Jim
New est. diff = 1748
Think first time it dropped right after a new diff adjustment
Think first time it dropped right after a new diff adjustment
Z
02:56
Zack
no, it dropped like this before, and even deeper
02:57
I was wrong, it was only like 18 minutes per block that time, and we are 20 now.
IP
02:59
I P
well the problem right now is people ramp up diff with rented hashpower and leave
02:59
we are left with high diff low hashrate and get less rewards,m they wait for diff to drop again, hop on, get rewards and leave
MF
03:01
Mr Flintstone
diff has never dropped
IP
03:02
I P
updated and resynced my node
03:02
don't know what caused it to do out of sync
03:10
Deleted Account
aws mining not profitable anymore
03:10
if it ever was xD
IP
03:11
Deleted Account
yeah
IP
03:11
I P
but in the long run of course amazon rental mining should not be profitable
03:12
i guess when we are back to 10min block time hitting network hard with amazon rental could be profitable
MF
03:12
Mr Flintstone
do you think the difficulty will go down at 14000?
Z
03:12
Zack
I think if we all use the same kind of mining hardware and software, then it becomes unstable and the difficulty could start oscillating.
If there is variety in our strategy, then it is more stable and less likely to oscillate.
I am trying to calculate the limits of the supply curve that can result in the stable mode.
If there is variety in our strategy, then it is more stable and less likely to oscillate.
I am trying to calculate the limits of the supply curve that can result in the stable mode.
JS
03:15
Jon Snow
this could be mined by ASICs in the future as well
OK
03:17
O K
Everything's gravy guys, let's give it a day or two and see what's up
Z
03:31
Zack
The forumula for retargeting now is assuming that the number of miners wont change when the difficulty changes. This is not the case.
I think if we take the geometric mean between the 2 difficulties, and use that instead. It might work a lot better. I am writing this up more formally with math to be sure.
I think if we take the geometric mean between the 2 difficulties, and use that instead. It might work a lot better. I am writing this up more formally with math to be sure.
03:51
Deleted Account
03:52
why there is no any info after block 11961?
OK
03:56
O K
There is info, those blocks just aren't considered confirmed yet by amoveopool standards
04:00
Deleted Account
oh,there is no reward for me last 6 hours
04:01
i seems not normal
OK
04:02
O K
Things block times have slowed dramatically since we hit 12000 around 5 hours ago
04:06
Deleted Account
and it has an effect on the block time before 12000?
OK
04:07
O K
I'm not sure I understand the question, but I'll take a look at your account when I get home if you'd like
04:09
Deleted Account
Does anyone know where I can get info on sex dating free ;)
04:10
So is it really just increased difficulty that is slowing down mining balances?
04:10
Mine has seemed stuck for quite some time...
MF
04:11
Mr Flintstone
buying veo
04:12
pm me
OK
J
06:47
Jim
Quite reasonable block times, hm. Diff estimate spiked as usual
MF
06:48
Mr Flintstone
why did it spike? Aren’t we still experiencing >10min blocks
J
06:48
Jim
Part of the median calculation
06:49
Several blocks in short interval skews calculation to be shorter
06:49
It sort of evens out after 2000 blocks
06:50
Deleted Account
Is anyone getting anything much from mining? I went from solid movement to almost nothing in the past few hours?
Z
06:51
Deleted Account
Was it that huge of an increase?
Z
06:51
Zack
https://github.com/zack-bitcoin/amoveo/blob/master/docs/design/retargetting_stability.md
I started making a document exploring why our current retargeting might not be ideal.
I started making a document exploring why our current retargeting might not be ideal.
06:53
It seems to me that as the profit margin gets smaller, the retargeting becomes less stable, and we are more likely to end up in a oscillating state.
So we could dampen the movements a little to prevent the oscillation.
So we could dampen the movements a little to prevent the oscillation.
J
06:54
Jim
Yeah, I think median retargeting may introduce some skewness, haven’t really looked at the data
Z
06:55
Zack
using medians is important for preventing timestamp attacks.
06:58
Deleted Account
2 1080ti whole night get 0.06 veo
Z
07:29
Zack
I am starting to think that all oscillations are not necessarily bad.
07:29
As long as enough people are mining and making a profit so we keep getting blocks, then it is going well.
Both the fast mode and slow mode are different competitions that suit different kinds of miners.
They are both effective at converting electricity into Veo. It is hard to tell which is more effective, and for that reason it is good to do both. It reduces our risk.
Both the fast mode and slow mode are different competitions that suit different kinds of miners.
They are both effective at converting electricity into Veo. It is hard to tell which is more effective, and for that reason it is good to do both. It reduces our risk.
07:30
Deleted Account
This is going to take some getting used to...I went from getting .01 coins per every 10 minutes or to now getting nil
Z
07:30
Zack
what is bad is if the size of the oscilation is increasing each time.
IP
07:31
I P
In reply to this message
the most effective way is mine and hodl=) given that VEO gets actual use of course=)
07:32
Deleted Account
At this point once I get one, I probably won't sell for less than $200 each
07:32
With how long it's going to take
IP
07:33
so people will still sell
07:33
Deleted Account
the bitcoin difficulty adjustment is smooth. Why can't we just retarget like that
IP
07:34
I P
diff will go down because right now it is for sure more than it should be
07:34
it is smooth because if you turn off or on couple of thousand of asics it won't really change that much in btc network
Z
OK
07:35
O K
Bo, you could mine on the Eth chain for a whole week with your rig and be lucky to get $6 worth of Eth
IP
07:35
I P
VEO network is only building
OK
07:35
O K
Not the point
IP
07:36
I P
the point is miner profit is low right now
07:36
and i think it is a good thing
OK
07:37
O K
I don't even think it's that low, it's low for people renting hardware from datacenters ...
IP
07:37
I P
actually i must confess, there are at least 2 coins which i dumped with nicehash just because it was too profitable to mine them at that time
07:37
i bought orders on nicehash, got a lot of coins fast and dumped them
OK
N
08:34
NM$L
what‘s the mining cost now?
08:34
per veo
OK
08:48
O K
Are you using the randomstring parameter? Generally caused by an inadequate randomstring
08:56
Deleted Account
Ahh okay ty
08:56
Yes i am
08:56
Will it effect my mining?
OK
08:56
O K
That share is wasted, if it's not happening very often I wouldn't worry about it
08:56
Deleted Account
Ty :)
OK
08:56
O K
:)
09:08
Amoveopool2.com was doing well on the new node, but once Zack's pool found a block, the new node was left behind (not given updated headers). I manually downloaded the headers for that block and added it to the peers list (but doing so did not cause it to show up as a peer on my other node). I'm switching back to the other .9 node for now since I don't know if the problem will persist overnight, which would result in a fork. This fork was a cause of the long blocktime for block 12028
09:11
I'm leaving the 45.77.196.69 node running with the manual changes, to see what happens, but it may be necessary for now to add 45.77.196.69 to the default peers list, along with the .4 node.
09:24
Deleted Account
why does amoveopool2 not support explorer on phone
09:24
can't type in miner address in all explorer i have tried
OK
09:26
O K
I'm not sure bo, I don't honestly use it on the phone but I'll add it to my list to look at tomorrow morning. What OS, what browser?
09:35
Deleted Account
iphone chrome
09:35
Safari
10:12
Deleted Account
So this was probably already outlined, and I missed it, but what happened to blocks 11985-12026?
10:13
Sorry, it changed....11984-12031
10:13
10:14
I mean it explains why my pending balance hasn't moved at all today lol
11:28
Deleted Account
difficulty is too high.
11:29
with 2 1080ti. I can hardly get 0.1 veo
I
11:29
Iridescence
Anybody here running a 1060?
11:33
Deleted Account
60 blocks per day. it will need a month to reach the next adjustment
11:35
this is wasting time and electricity indeex
11:38
Deleted Account
So on 2 1080Ti's, if you're getting .1 VEO per day that's still $10 per day based on a $100 valuation, which it's about 50% higher than that last I checked, but let's just say $100.
11:38
I'd be lucky to get that on ETH on 5 1070Ti's
11:39
So I don't think it's time to kick the bucket on mining imo, but it's your rig
M
11:44
Mike
Any AMD miner?
11:48
Deleted Account
reward is so low that never will cover my payment on cards
11:50
mining with AWS gpu seems not profitable anymore
11:52
Deleted Account
Oh if you're renting, then no
12:59
Deleted Account
in such difficulty, amoveo is dying. 60 blocks per day. we need a month to get next adjustment. Why can't we make a change every 200 blocks
IP
13:36
I P
In reply to this message
there should be like 144 blocks per day, right? 60 a day is harsh, damn. Yeah, looks like amazon gpu rental is out of the game at least until next diff adjustment which will bring diff down
14:04
Deleted Account
70 blocks per day
14:06
28 days to next adjustment
14:07
more and more miner will leave
M
14:10
Mike
Not a bad thing
G
S
15:08
Sy
thats what i said earlier...adjusts every x blocks is bitcoin 2009, not new coins 2018, its very crippling
IP
S
15:14
Sy
im pretty sure satoshi would have adapted his vision aswell with new knowledge being available
15:15
its not as bad the bigger you are but ive seen several small coins stranded in high diff, you grind it out once or twice but not much more often - lets wait and see if the big hashrate returns after diff drop
Z
15:45
Deleted Account
Hey Zack, few questions on calling "spend" API via HTTP. I've been looking through the code/docs but I wanted to ask/confirm a few things: (1) Is the fee subtracted automatically from the amount? If I send 1, will the recipient get (1 - 0.00152050)? (2) The API does not return the transaction hash of the newly created spend transaction, correct? If that's right, is there a straightforward way to get that transaction hash? Does that involve tx_pool:get() somehow? (3) Batching is not possible at the moment, correct? At least, I cannot see how to create a transaction with multiple recipients/amounts.
Z
15:48
Zack
1) no. The spender pays the fees, not the receiver.
2) the TX hash is a meaningless value. You couldn't do anything useful with it.
3) each spend TX has one sender and one receiver.
2) the TX hash is a meaningless value. You couldn't do anything useful with it.
3) each spend TX has one sender and one receiver.
15:51
Deleted Account
Thanks for the help. So on (1), if I want someone to receive 1 I would send them (1 + 0.00152050) from my end. And On (2), can't the TX hash be used to see if it was included in a block? Isn't it possible for a TX to eventually be 'evicted' from the mempool after a long-ish period of time? Or is it guaranteed to eventually be included in a block once it's in the mempool?
Z
15:53
Zack
1) false. That would give them more than 1.
2) false.
A tx in the mempool might get deleted, especially if no other node stores the tx in their mempool.
2) false.
A tx in the mempool might get deleted, especially if no other node stores the tx in their mempool.
15:57
Deleted Account
Ok so the fee is simply deducted in the "background" from my account, I don't actually adjust the amount I'm sending via API by the fee amount. Got it. Thanks for the help.
16:07
Deleted Account
so we will wait a month for the next adjustment?
Z
16:13
Zack
I think it will take less than 20 days till the next retargeting.
16:44
Deleted Account
then I will turn off my miner and wait for the next adjustment.
16:45
the noise and heat is huge in fact
S
16:46
Sy
and thus the cycle begins
16:50
Deleted Account
normally i won't get more than 1/1000 of the blocks mined. So I will get 2 veo in the coming month. I'd better have a rest and wait for the next adjustment.
IP
16:56
Faster retargetting is better for sure
S
16:58
Sy
chances are high tho that the hashrate will return, current diff will be normal diff and the next one will be higher, business as usual ^^
17:03
Deleted Account
Just don't understand why there are 4x difficulty than last adjustment
17:04
in bitcoin, the difficulty increasement is 10％ each. 4x only harm the miners.
17:04
Deleted Account
gm guys
17:05
total circulation on amoveo?
17:05
Also if anyone sells amoveo can dm me
P|
17:07
Paul N. | BAND (🅑) - I'll never DM you
In reply to this message
the difficulty level is an effort to keep the block time at 10 minute/block. it was previously 2.5 mins/block, thus the difficulty adjust 4x so that the block time become 10 mins as intended. Which part do you not understand?
Z
17:08
Zack
In reply to this message
https://en.bitcoin.it/wiki/Target
According to this, bitcoin difficulty can change by a maximum of 4x.
According to this, bitcoin difficulty can change by a maximum of 4x.