Amoveo β₯π§Ώ
Previous messages
Next messages
21 February 2018
MH
04:31
Mandel Hoff
Agreed on the 1/10 sec.
04:33
Any idea what epoc is? Seems like epoc is ~402 days ago.
04:33
34750406 / 60 / 60 / 24 = ~402 days
Z
04:34
Zack
I haven't heard of "epoc" before.
MH
04:34
Mandel Hoff
Epoc is the time if that value was 0. Unix epoc time is something like Jan 1, 1970.
Z
04:35
Zack
https://github.com/zack-bitcoin/amoveo/blob/master/apps/ae_core/src/consensus/constants.erl#L62
Looks like it is 1482574978 seconds after the Unix epoc.
Looks like it is 1482574978 seconds after the Unix epoc.
04:36
I probably wrote this part of the code ~402 days ago.
MH
04:39
Mandel Hoff
Yes, your block chain epoc is 12/24/2016 @ 10:22am (UTC). Fun.
04:40
Any idea if this will break due to the year 2038 problem?
https://en.wikipedia.org/wiki/Year_2038_problem
https://en.wikipedia.org/wiki/Year_2038_problem
Z
04:50
Zack
https://github.com/zack-bitcoin/amoveo/blob/master/apps/ae_core/src/consensus/chain/headers.erl#L144
https://github.com/zack-bitcoin/amoveo/blob/master/apps/ae_core/src/consensus/constants.erl#L63
It is good you realized this.
It wouldn't be that hard to solve it with a hard fork later, but this is something I would like to do right from the beginning.
https://github.com/zack-bitcoin/amoveo/blob/master/apps/ae_core/src/consensus/constants.erl#L63
math:pow(2, 32) / 365 / 24 / 60 / 60 / 10.looks like we have about 13 and a half years until this would be a problem.
13.619251953323186
It is good you realized this.
It wouldn't be that hard to solve it with a hard fork later, but this is something I would like to do right from the beginning.
Deleted joined group by link from Group
05:26
Deleted Account
is sha256 the only logarithm for mining?
Z
G
05:44
Gonzalo
Zack I've seen many times that my balance goes +1 and minutes later -1. I suppose that I've found a block that was already mined, so basicaly my miner has been "waisting time". Am I right?
Z
05:47
Zack
that might be.
Maybe someone else with a faster miner has a bug where they are ignoring your blocks
Maybe someone else with a faster miner has a bug where they are ignoring your blocks
G
05:50
Gonzalo
In reply to this message
Or maybe my miner is failing at reporting the minted block to the network?
05:51
Just guessing, I really don't know
06:01
Deleted Account
Zack what GPU miner do you recommend using for mining?
Z
06:02
Zack
In reply to this message
none exists. I am writing it now. https://github.com/zack-bitcoin/amoveo-opencl-miner
MH
06:27
Mandel Hoff
In reply to this message
Very likely your mined blocks are becoming Orphans. This was happening very often yesterday when difficulty was low. I'm sure it's still happening. Odds are based on: block propagation time ~5 sec, how often your miner checks in for new work, block time, etc...
06:44
Deleted Account
In reply to this message
You are not alone plus i mined 1 block in 20 minutes which is ridiculus conpared with yesterday mining
Z
06:45
Zack
it is supposed to take 10 minutes for the network to mine a block.
So if there are 3 miners each with the same power, then each person would find a block every 30 minutes.
So if there are 3 miners each with the same power, then each person would find a block every 30 minutes.
G
06:47
Gonzalo
In reply to this message
Also diff is higher now and you're competing against more miners than yesterday
06:48
(ae_core_prod@scw-9653e4)29> peers:all().
[{{209,250,250,137},8080},
{{199,247,25,21},8080},
{{159,65,44,147},8080},
{{159,65,134,21},8080},
{{159,65,182,117},8080},
{{162,218,209,18},8080},
{{178,152,171,191},8080},
{{51,15,69,135},8080},
{{52,234,133,196},8080},
{{51,15,212,91},8080},
{{176,9,84,75},8080},
{{73,232,25,43},8080},
{{159,89,106,253},8080}]
06:48
Deleted Account
In reply to this message
Are you facing server crashes and talk helper fail error as well ?
G
06:49
Gonzalo
yes:
06:49
got this data
["mining_data"]
mining data block hash is [-7,[-7,169,231,8,73],8080]
"J1zS/1WCxYhes/IFLiDb/d+25gCQdy82mVxkt4WK504="
talk_helper failed_connect 1
[-7,[-7,209,250,250,137],8080]
talk_helper failed_connect 1
syncing with peer [-7,[-7,51,15,69,135],8080]
trade peers
server crashed.
talk helper fail
get their top header
already synced with this peer
06:50
but appart from that, the networks looks pretty healthy today
06:51
Deleted Account
Me neither
Z
06:51
Zack
As I have said several times now. This can all be safely ignored.
Erlang is a fail-fast language, and the internet is imperfect. So it is impossible to completely get rid of errors.
I could make them all silent by pushing them to the log file, but I think this will make it harder for you guys to give me useful reports when things go wrong.
Erlang is a fail-fast language, and the internet is imperfect. So it is impossible to completely get rid of errors.
I could make them all silent by pushing them to the log file, but I think this will make it harder for you guys to give me useful reports when things go wrong.
06:53
In order from best to worst, this is how we can share code in this telegram group:
1) copy paste inside triple back-ticks
2) copy paste as plain text
3) a screenshot
4) a photo of your monitor
1) copy paste inside triple back-ticks
like this
2) copy paste as plain text
3) a screenshot
4) a photo of your monitor
06:53
Is there a way for me to turn off the ability to share photos?
G
07:07
Gonzalo
Zack I believe that maybe block propagation should be faster:
1- about 4 minutes ago I minted block 6101, my explorer.html shown that was me who found it
2- after more than 2 minutes later your explorer.html shown height 6101, and says that was other miner who found it (I've been refreshing the balance)
1- about 4 minutes ago I minted block 6101, my explorer.html shown that was me who found it
2- after more than 2 minutes later your explorer.html shown height 6101, and says that was other miner who found it (I've been refreshing the balance)
Z
07:08
Zack
maybe whoever mined 6101 is using old software that shares blocks more slowly.
MH
07:09
Mandel Hoff
Did the same person who got 6101 also get 6102? Sometimes they can ignore your 6101 if they get 6102 first.
07:10
Or, maybe you were ignoring their 6101.
G
07:10
Gonzalo
woow, this is weird... now the situation reversed... your explorer says that was me who did 6101 and my explorer says was the other... I've got screenshots if you want...
Z
07:11
Zack
my mistake. no 6102.
G
07:11
Gonzalo
now my node sees 6102
07:12
Deleted Account
I see 6101 on light node
07:12
Its same on explorer
G
07:13
Gonzalo
I see 6102 on my node and also on amoveopool, but not on Zack's node,
MH
07:13
I'm pretty sure I didn't mine it though. I haven't been mining.
G
Z
07:14
Zack
I finally got 6102, and it changed my 6101 as well.
07:14
Deleted Account
Same here
G
07:14
Gonzalo
In reply to this message
But even If you are not mining, your pool is updating the height I believe
MH
07:15
Mandel Hoff
Yes, as far as I know my node is in a valid state.
G
Z
07:15
Zack
In reply to this message
the mining pool doesn't know what a "height" is.
Your amoveo full node should be automatically syncing with blocks, as long as you have a publicly facing ip address where people can send you blocks.
Your amoveo full node should be automatically syncing with blocks, as long as you have a publicly facing ip address where people can send you blocks.
G
Z
07:17
Zack
oh, right
G
07:17
Gonzalo
he's got a blockchain height counter
07:20
well, now with block 6103 the propagation went faster. I'm comparing times between my node, Zack's and Mandel's
07:21
wow, now at 6106
07:21
Deleted Account
I found 3 of them is it what they call luck ?
MH
07:22
Mandel Hoff
Wow, that's a big jump.
G
07:22
π
Z
07:22
Zack
The network will behave differently once we have more nodes.
The ideal protocol at this small network size would be to push the blocks to everyone as soon as you find them.
but that protocol doesn't work as the number of nodes increase, it would cause too much bandwidth spam
The ideal protocol at this small network size would be to push the blocks to everyone as soon as you find them.
but that protocol doesn't work as the number of nodes increase, it would cause too much bandwidth spam
G
07:22
Gonzalo
so you are BPILU6la9xcs8?
MH
07:22
Mandel Hoff
For reference, my pool stats page has a 20 second cache on it. Don't use the web page directly for measuring block propagation time.
G
G
07:23
Gonzalo
hehe
07:24
Deleted Account
Can you check accounts balance from just pubkey ?
G
07:25
have a look at http://159.89.106.253:8080/explorer.html
07:26
you have 303 VEO, so you have more CPU power than luck
Z
G
07:27
Gonzalo
thanks, I was not aware of this
07:28
Deleted Account
oh, didnt realise you could just copy the key by looking up block number and then load it up in pubkey to check balance. Now im gonna see who has most balance
07:29
G
07:29
Gonzalo
Zacks gonna kill you! π
07:30
Deleted Account
when i click account lookup account it doesnt show me balance on explorer ? am i missing something
Z
07:31
Zack
maybe you copy-pasted wrong.
07:31
for me it says you have 304
07:32
Deleted Account
not really i hope to take lead on cpu mining but when gpu miner launches i will be at one corner. Oh thanks i didnt see.
G
07:34
Deleted Account
In reply to this message
no i tried several times now. Explorer doesn't show me my balance
G
07:35
Gonzalo
where are you looking at?
Z
07:35
Zack
http://159.89.106.253:8080/explorer.html
BPILU6la9xcs8qNVG4hgC3654WR5n0pts1fNmMfVrlVOw4eWkGJqvi3q/1T0gJ8cfTOF/fWA4OtQhYUMmyxTZjs=
BPILU6la9xcs8qNVG4hgC3654WR5n0pts1fNmMfVrlVOw4eWkGJqvi3q/1T0gJ8cfTOF/fWA4OtQhYUMmyxTZjs=
G
07:36
Gonzalo
it's working for me
07:36
BPILU6la9xcs8qNVG4hgC3654WR5n0pts1fNmMfVrlVOw4eWkGJqvi3q/1T0gJ8cfTOF/fWA4OtQhYUMmyxTZjs=
07:37
Deleted Account
In reply to this message
oh it works without = on light node. So i didnt put that on explorer. Thanks my mistake
G
07:39
Gonzalo
π
07:42
Deleted Account
now i can tell who has powerful cpu other than me
G
07:43
Gonzalo
yeah, keep us informed man π
07:43
Deleted Account
BKyLqCvF5vt7KBiPLId7xlW64Bb/uV+icPnvn5mgEKncqlCKiaXUTkRcZv7iYK3GKxSspNh0leIhc4YA+DJAY/s=
07:43
he has most powerful cpu he is really consistent in finding blocks
G
07:44
he has only 30
07:45
maybe he found them 1 week ago, when mining alone
07:46
Deleted Account
no i started putting block numbers from 6107 in reverse order on lookup_block. he always finds 4 or 3 in row and others address find them in random order.
G
07:47
Gonzalo
oh ok, at which height was this?
07:48
Deleted Account
from 6090 to 6092
07:49
other is 6094 to 98
07:51
found you BGDXGmovuTEr3CFfzY0xr0zXS3purkIPPZsljZv4gvQe87K6W8be1IpwDwmqhgcSIlhTvb9Q7pgrl+h2dmXGEXM=
07:51
guess who is this
G
07:51
Gonzalo
oh I see, I think you are right
07:52
Deleted Account
yea and that address mined half the blockchain
07:54
little more than half actually π
Z
07:56
Zack
BGDX is the node with the mining pool that the light node connects to by default.
G
07:57
Gonzalo
π
Z
07:58
Zack
Its balance is too high. people must have been mining when the keys were locked.
07:59
Deleted Account
In reply to this message
keys locked or unlocked how does it help them mining ?
Z
08:00
Zack
if you don't decrypt your private key, then you can't spend tokens.
08:00
keys:unlock("").
MH
08:03
Mandel Hoff
I updated http://amoveopool.com/pool
Now it shows last ~10 confirmed blocks, timestamps, and coin base addresses. "Confirmed blocks" are delayed a bit to ignore this orphan problem at the top of the chain.
Now it shows last ~10 confirmed blocks, timestamps, and coin base addresses. "Confirmed blocks" are delayed a bit to ignore this orphan problem at the top of the chain.
G
08:04
Gonzalo
great!
08:05
it shows block reward 0.99 are you being exact here..?
MH
08:06
Mandel Hoff
Mining shares should be credited better. There's a delay before credits go to unpaid balance due to waiting for "confirmed blocks". Payouts work fine, but txs can get lost. They should get lost much less with longer block times and any tx sharing fixes Zack implements.
08:07
Block reward is 1.0, but I have some double rounding coding to clean up before I can payout 1.0.
08:09
Deleted Account
In reply to this message
mining pool is hard to code and i have heard its also complicated.
08:21
Deleted Account
I'm trying to resynch my database.. and getting block absorber died!
G
08:35
Gonzalo
Usman which CPU have you got? Just curiosity..
Z
08:37
Zack
In reply to this message
error messages should be ignored unless you notice something working incorrectly.
08:41
Deleted Account
for whatever reason I'm not synching the database.. I tried make prod-restart and quick..
08:41
and not synching database
G
Z
08:46
Zack
In reply to this message
I still don't know very much about your situation.
Why do you think it is not syncing?
I bet your database got corrupted. if you try to turn on while ti is already on, it gets corrupted. or if you turn it off incorrectly.
Why do you think it is not syncing?
I bet your database got corrupted. if you try to turn on while ti is already on, it gets corrupted. or if you turn it off incorrectly.
09:03
Deleted Account
fixed.. i had to git pull
09:03
then prod-restart worked
Z
09:04
Zack
great
09:08
Deleted Account
also.. I didn't halt the node correctly which probably caused the problem to begin with..
09:08
api:off().
and
halt().
and
halt().
Z
09:10
Zack
yes, that makes sense
09:14
Deleted Account
are there any examples of the governance working on testnet?
Z
09:15
Zack
we started updating the block reward. the market hasn't been closed.
09:15
Deleted Account
got a link?
Z
09:15
Zack
I don't know what you want me to link you to.
09:16
Deleted Account
well what do you mean you're starting to update the block reward, i assume this is being done on a market i can particpate in?
Z
09:30
Deleted Account
Ryan, amoveo won't be any markets for now. Just for miners at the moment.
Z
09:30
Zack
In reply to this message
the markets are working. you can do them from the light node too.
09:31
Deleted Account
Really.
09:34
Damn, good stuff
10:02
Deleted Account
in the miner.erl file... I want to setup to connect to my own node.
%-define(Peer, "http://159.65.134.21:8081/").%for a full node on same computer.
%-define(Peer, "http://localhost:8085/").%for a mining pool on the same computer.
-define(Peer, "http://159.89.106.253:8085/").%for a mining pool on the server.
-define(CORES, 2).
-define(mode, pool).
-define(Pubkey, <<"BMjV7rAAssU+DGd8w+6XsyDSdgoichddlSipZT3U+jehHSD68UwPdF9TO3HQ0g4hCh2rgUQyqPnP7vP0i/l8Ijw=">>).
%-define(Peer, "http://159.65.134.21:8081/").%for a full node on same computer.
%-define(Peer, "http://localhost:8085/").%for a mining pool on the same computer.
-define(Peer, "http://159.89.106.253:8085/").%for a mining pool on the server.
-define(CORES, 2).
-define(mode, pool).
-define(Pubkey, <<"BMjV7rAAssU+DGd8w+6XsyDSdgoichddlSipZT3U+jehHSD68UwPdF9TO3HQ0g4hCh2rgUQyqPnP7vP0i/l8Ijw=">>).
10:03
mode, pool would be changed to what?
G
10:03
Gonzalo
don't touch that
10:03
Deleted Account
ok
Z
10:03
Zack
use "for a full node on the same computer"
10:04
right now it is set up to connect to the mining pool I am maintaining.
10:04
Deleted Account
i see that
10:04
I'm running my own full node
10:04
on a separate system
10:05
and connect to my own full node
Z
10:05
Zack
then you would need to install a mining pool on the computer that is running the full node.
10:05
Deleted Account
ok got it
10:05
and then just change the ip address and pubkey?
Z
10:05
yes
10:06
Deleted Account
yep.. I'm following the directions, the pool part got me confused.. thanks..
G
10:07
Gonzalo
In reply to this message
I was refering to "mode, pool would be changed to what?". -I suppose that he was refering "-define(mode, pool)."
10:08
Deleted Account
yes.. I'll just make my full node a mining pool and all good
10:17
i created keys on my node.. and when i check for the pubkey.. it gives me.
<<4,83,104,158,196,42,151,105,194,220,190,244,43,159,79,
120,106,238,190,228,111,240,78,1,65,5,121,215,246,...>>
<<4,83,104,158,196,42,151,105,194,220,190,244,43,159,79,
120,106,238,190,228,111,240,78,1,65,5,121,215,246,...>>
Z
10:18
Zack
api:pubkey().
13:56
I have some people mining against my pool already
13:59
talk_helper failed_connect 1
14:00
I"m getting this talk_helper error alot.. is this a real problem?
14:00
I'm seeing "mining_data" on my node so I have to assume everything is working
14:25
Deleted Account
so block height is 6163, and not changing
14:33
so I mined 6164. and my balance went from 0 to
100227592
100227592
14:34
i was expecting my balance to be 1
14:37
everything seems to be working, and the block I mined 6164 took a while to be reflected in the light node, but it did eventually.. like 10 min or so I guess
14:48
so i keep getting this error.
14:48
Found a block. 1
read nonce n is 2
If you are running a solo-mining node, then this error may have happened because you need to turn on and sync your Amoveo node before you can mine. You can get it here: https://github.com/zack-bitcoin/amoveo
If this error happens while connected to the public mining node, then it can probably be safely ignored.server gave confusing response
server gave confusing response
server gave confusing response
server gave confusing response
Found a block. 2
read nonce n is 2
If you are running a solo-mining node, then this error may have happened because you need to turn on and sync your Amoveo node before you can mine. You can get it here: https://github.com/zack-bitcoin/amoveo
If this error happens while connected to the public mining node, then it can probably be safely ignored.server gave confusing response
server gave confusing response
server gave confusing response
server gave confusing response
Found a block. 2
14:48
I'm mining but with my own full node / mining pool server
14:51
200455184 <.. so the print out doesn't show a period, but this would be 2.00455184 VEO
14:55
My node is at block height 6167, and I've mined 3 blocks
14:56
The light wallet is at block 6164
G
15:10
Gonzalo
My experience is that the node only syncs automatically when mining inside it with "mine:start()." or when c-mining on the same server. Don't know about your config with the pool.
15:11
Maybe you could try also mining inside just to keep the node updated
15:12
Anyway better wait for Zack's advise
15:22
Deleted Account
the problem is my node is updated, but the light wallet node is 3 blocks behind
15:23
so not sure what's up with that
15:23
I'm just letting it run, and see what happens
15:28
block height is 6168, so I'm synching blocks from other full nodes
15:28
my last block mined was 6167
15:30
I'm getting alot of server crashed, and talk helper fail, but mining blocks, and also synching from other nodes
M
16:10
Mike
I think the whole thing is not mainnet-ready yet.
Z
Z
18:00
In reply to this message
Can you be more constructive? What do you think Amoveo needs?
Why do you think it would be more effective for me to write it as a volunteer, instead of incentivizing a community to work together?
It seems to me that things move a lot faster with more eyeballs looking at it.
Why do you think it would be more effective for me to write it as a volunteer, instead of incentivizing a community to work together?
It seems to me that things move a lot faster with more eyeballs looking at it.
18:14
Deleted Account
Even though I still did not have time to setup a rig for Amoveo support (Kids and fulltime job) I am with Zack on this better to start and if it breaks fix and continue so far seems like people on the testnet are not losing their veos
G
G
20:13
Gonzalo
π thanks
m
20:54
manu
@zack your node is synchronized??
Z
20:55
Zack
there might be a problem. it says it has one more header than blocks
20:58
Deleted Account
(ae_core_prod@usman-GE70-2PC)1> sync:start().
[-7,[-7,178,152,136,153],8080]
talk_helper failed_connect 1
[-7,[-7,159,89,106,253],8080]
syncing with peer [-7,[-7,159,89,106,253],8080]
trade peers
ok
get their top header
get headers
give blocks
server crashed.
talk helper fail
they are not accepting our blocks.(ae_core_prod@usman-GE70-2PC)2>
[-7,[-7,178,152,136,153],8080]
talk_helper failed_connect 1
[-7,[-7,159,89,106,253],8080]
syncing with peer [-7,[-7,159,89,106,253],8080]
trade peers
ok
get their top header
get headers
give blocks
server crashed.
talk helper fail
they are not accepting our blocks.(ae_core_prod@usman-GE70-2PC)2>
20:58
should i ignore this error..?
21:03
it happened again my node shows 368 while explorer shows 331
21:03
Z
21:03
Zack
my server got stuck.
21:07
Deleted Account
In reply to this message
yeah. It doesn't show my balance on light node but block explorer is working
21:08
meaning my database got corrupted.
21:08
what could be the main cause for this .?
Z
21:15
Zack
no, this time my database got corrupted.
I am restarting my server.
I am restarting my server.
21:21
Deleted Account
In reply to this message
Okay π. I did prod-clean twice already. I will wait for your server to go online to sync my node again.
Z
22:48
Zack
A bunch of problems came up because there are so many people in the network now. So just now I updated the code on github to fix these things.
Now you don't ask your peers for you ip address so frequently. you only do it once, and you store your ip address in ram for later.
Now we add peers to the blacklist more quickly if the peer is failing to respond, and we keep the peers in the blacklist a longer time.
Now you don't ask your peers for you ip address so frequently. you only do it once, and you store your ip address in ram for later.
Now we add peers to the blacklist more quickly if the peer is failing to respond, and we keep the peers in the blacklist a longer time.
22:49
If you are running an Amoveo full node, update soon.
22:54
Deleted Account
I'm trying to sequence to update server WITHOUT corrupting my database..
api:off().
halt().
make prod-stop
git pull
make prod-go
make prod-attach
api:off().
halt().
make prod-stop
git pull
make prod-go
make prod-attach
22:54
hope this is correct
Z
22:56
Zack
I would do it like this
api:off().
halt().
git pull
make prod-restart
22:57
Deleted Account
ok thanks
Z
23:00
Zack
ok, I am all synced up.
23:05
I see someone set up their amoveo node to use a different port.
So i will update the code to make it easier to select a port.
So i will update the code to make it easier to select a port.
23:12
Deleted Account
I'm gettng alot of peers not accepting my blocks
23:12
due to them not updated yet?
Z
23:12
Zack
yeah, a lot of peers probably died from the old broken code base. The same way my server did.
23:13
Deleted Account
ok
Z
23:13
Zack
hopefully your node will blacklist them and remove them from your list of peers.
23:13
Deleted Account
yes, doing so now
23:13
removing peer [-7,[-7,37,211,192,130],8080]
Z
23:14
Zack
great
23:18
Deleted Account
removing peer [-7,[-7,203,80,236,230],8080]
(ae_core_prod@usman-GE70-2PC)6> sync:start().
syncing with peer [-7,[-7,159,203,4,195],8080]
trade peers
ok
talk_helper failed_connect 1
removing peer [-7,[-7,159,203,4,195],8080]
(ae_core_prod@usman-GE70-2PC)7> api:balance().
29166229272
talk_helper failed_connect 1
removing peer [-7,[-7,159,203,4,195],8080]
(ae_core_prod@usman-GE70-2PC)8> api:height().
6182
(ae_core_prod@usman-GE70-2PC)9> block:height().
6057
(ae_core_prod@usman-GE70-2PC)10> sync:start().
syncing with peer [-7,[-7,178,152,171,191],8080]
trade peers
ok
(ae_core_prod@usman-GE70-2PC)6> sync:start().
syncing with peer [-7,[-7,159,203,4,195],8080]
trade peers
ok
talk_helper failed_connect 1
removing peer [-7,[-7,159,203,4,195],8080]
(ae_core_prod@usman-GE70-2PC)7> api:balance().
29166229272
talk_helper failed_connect 1
removing peer [-7,[-7,159,203,4,195],8080]
(ae_core_prod@usman-GE70-2PC)8> api:height().
6182
(ae_core_prod@usman-GE70-2PC)9> block:height().
6057
(ae_core_prod@usman-GE70-2PC)10> sync:start().
syncing with peer [-7,[-7,178,152,171,191],8080]
trade peers
ok
23:19
it is stuck at 6057 for a while now
Z
23:21
Deleted Account
Yes
23:22
I updated when u posted about your update
Z
23:22
Zack
did you restart from block 0?
23:23
Deleted Account
yes
Z
23:24
Zack
did you try doing
sync:start(). again?
23:24
maybe the first person you synced with didn't have all the blocks
23:24
Deleted Account
yes my block absorber died in between
23:25
so i did sync:start(). thrice to reach this block
23:25
i updated again and there was a change of one file
23:25
should i do make prod-clean again..?
Z
23:26
Zack
I am not sure why it wont sync the last 100 blocks. if you find anything out, please share.
23:27
Deleted Account
absorb block 6148
absorb block 6149
prune block 6120
prune block 6121
prune block 6122
prune block 6123
prune block 6124
prune block 6125
prune block 6126
prune block 6127
prune block 6128
prune block 6129
absorb block 6150
absorb block 6151
absorb block 6152
absorb block 6153
server crashed.
server crashed.
absorb block 6154
absorb block 6155
server crashed.
absorb block 6156
server crashed.
server crashed.
server crashed.
talk_helper socket closed remotely
talk helper fail
server crashed.
server crashed.
talk_helper socket closed remotely
talk helper fail
server crashed.
talk_helper socket closed remotely
talk_helper socket closed remotely
talk helper fail
talk helper fail
talk_helper socket closed remotely
talk helper fail
server crashed.
server crashed.
absorb block 6149
prune block 6120
prune block 6121
prune block 6122
prune block 6123
prune block 6124
prune block 6125
prune block 6126
prune block 6127
prune block 6128
prune block 6129
absorb block 6150
absorb block 6151
absorb block 6152
absorb block 6153
server crashed.
server crashed.
absorb block 6154
absorb block 6155
server crashed.
absorb block 6156
server crashed.
server crashed.
server crashed.
talk_helper socket closed remotely
talk helper fail
server crashed.
server crashed.
talk_helper socket closed remotely
talk helper fail
server crashed.
talk_helper socket closed remotely
talk_helper socket closed remotely
talk helper fail
talk helper fail
talk_helper socket closed remotely
talk helper fail
server crashed.
server crashed.
23:28
rest is server crashed errors
Z
23:29
Zack
what is
maybe there is a problem with automatically switching to normal mode.
sync_mode:check(). for you?maybe there is a problem with automatically switching to normal mode.
23:30
Deleted Account
i did sync_mode:quick().
Z
23:30
Zack
right.
23:31
Deleted Account
it could be that but i deleted the database and doing it all over again to see if this error persist
Z
23:31
Zack
so, what is sync_mode:check(). for you?
23:33
Deleted Account
In reply to this message
my node is downloading blocks from zero . i will let you know if it stops like before
Z
23:33
Zack
cool
23:40
Deleted Account
absorb block 995
absorb block 996
absorb block 997
absorb block 998
absorb block 999
talk_helper socket closed remotely
talk helper fail
removing peer [-7,[-7,159,89,106,253],8080]
(ae_core_prod@usman-GE70-2PC)3> sync_mode:check().
quick
(ae_core_prod@usman-GE70-2PC)4> sync:start().
syncing with peer [-7,[-7,37,228,235,74],8080]
trade peers
ok
talk_helper failed_connect 1
removing peer [-7,[-7,37,228,235,74],8080]
talk_helper failed_connect 1
removing peer [-7,[-7,37,228,235,74],8080]
(ae_core_prod@usman-GE70-2PC)5>
absorb block 996
absorb block 997
absorb block 998
absorb block 999
talk_helper socket closed remotely
talk helper fail
removing peer [-7,[-7,159,89,106,253],8080]
(ae_core_prod@usman-GE70-2PC)3> sync_mode:check().
quick
(ae_core_prod@usman-GE70-2PC)4> sync:start().
syncing with peer [-7,[-7,37,228,235,74],8080]
trade peers
ok
talk_helper failed_connect 1
removing peer [-7,[-7,37,228,235,74],8080]
talk_helper failed_connect 1
removing peer [-7,[-7,37,228,235,74],8080]
(ae_core_prod@usman-GE70-2PC)5>
23:41
its been 5 mins
22 February 2018
Z
00:00
Zack
I pushed some more changes. maybe it will work better for you now.
00:07
Deleted Account
π
00:07
it is syncing for now
Z
00:08
Zack
cool
00:27
Deleted Account
it is synced but my balance is zero
00:29
turns out my previous key was deleted
00:30
Deleted Account
i need to back up my key also. just in case
00:31
is that documented? I saw where the file is contained so easy to get i suppose
00:31
Deleted Account
In reply to this message
good idea. my guess is probably with new update it deletes the previous key.
00:33
Deleted Account
that update my node seemed to synch from 0 but not sure.
00:33
Deleted Account
yes it is in _build prod rel ae_core keys
00:33
Deleted Account
yep saw that
00:33
thanks
00:34
Deleted Account
π
01:14
I seem to be mining a block.. every couple min right now
01:14
sometimes every 15 or 30 sec.
01:22
Found a block. 1
read nonce n is 2
Found a block. 2
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
Found a block. 1
read nonce n is 2
Found a block. 2
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
read nonce n is 2
Found a block. 2
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
Found a block. 1
read nonce n is 2
Found a block. 2
Found a block. 1
read nonce n is 2
Found a block. 2
did not find a block in that period
01:23
now I'm finding a block every few secs
01:23
Deleted Account
r u srs ?
01:23
how much is ur balance
01:23
Deleted Account
my balance was like 216 after about an hour at IHOP
Z
01:24
Deleted Account
more like 2165
Z
01:25
Zack
That is 21.65 Veo
01:25
Deleted Account
ok
01:25
Deleted Account
but i checked no one has 21 veo balance
01:25
are you sure you are mining right
01:25
Deleted Account
nope lol
01:26
full node / setup as a mining pool
01:26
Deleted Account
BElnKs5PpWTjRUVDKZT2RCZEGix+o033ggStzT3leVwqPdNoFyOvKtBsOSUlfknDHACDZV2UCm6l1kJXM3FeNV8=
01:26
Deleted Account
separate miner connected to full node
01:26
Deleted Account
is this you..?
01:26
Deleted Account
BFNonsQql2nC3L70K59PeGruvuRv8E4BQQV51/axUVAt4LDFCGf0F8Pz3zgg0dfubViC3FF45GtiVHoPguYBMhQ=
01:26
this is me I think
01:27
Deleted Account
you have 5
01:27
Deleted Account
I'm going to restart my node
01:27
Deleted Account
How's the documentations? I am going to try this week.
01:27
Deleted Account
where did you check your balance?
01:28
Deleted Account
Sticker
Not included, change data exporting settings to download.
π, 34.6 KB
01:28
Deleted Account
on my node
01:28
Deleted Account
what is your block height
01:28
api:height().
01:28
block:height().
01:29
Deleted Account
i can't get commands to work on my node
01:29
Deleted Account
first stop your miner
01:30
ctrl + c then a then sh clean.sh
01:30
then type command on your node
01:32
Deleted Account
i can't get the ctrl +c to do anything
01:32
so trying to something else
01:33
Deleted Account
01:34
this is where you put ctrl+ c this is how it should respond everytime
01:42
Deleted Account
ok for me ctrl and alt + c works
01:58
Deleted Account
my keys were also lost :(
01:59
starting over
G
02:04
Gonzalo
I just did git pull, I confirm my pubkey has changed as well
02:04
so byebye to my 78 fakeVEOs π
MH
02:05
Mandel Hoff
Somebody got the GPU working.
02:05
G
02:06
Gonzalo
wow
Z
02:06
Zack
Git pull shouldn't change your pubkey.
Make prod-clean shouldn't change your pubkey.
'rm -rf _build' does change your pubkey
Make prod-clean shouldn't change your pubkey.
'rm -rf _build' does change your pubkey
G
02:07
Gonzalo
I just did
api:off().
halt().
git pull
make prod-restart
02:08
Deleted Account
I've only used the above commands, and my pub key changed
02:08
system generated, no password
02:08
was locked.. had to unlock
02:09
node is stuck at 0 after commands issued, so waiting to see if it'll synch
Z
02:09
Zack
oh, my pubkey was changed too. I wonder what happened.
02:10
I figured out why. your old keys file is still there.
02:11
the old key file is in
The new location where we keep keys is
_build/prod/rel/ae_core/keys/keys.dbThe new location where we keep keys is
_build/prod/rel/amoveo_core/keys/keys.db
02:11
so you can just copy paste the file from the old location to the new one.
02:11
Deleted Account
ok
G
02:12
Gonzalo
nice
Z
02:12
Zack
This shouldn't happen again. It is just because we renamed all the folders with this update.
G
02:12
Gonzalo
renaming all has been probably a major update ;-)
Z
02:13
Zack
I didn't even do it. Someone made a pull request
G
02:13
Gonzalo
Yes I saw
Z
G
02:13
Gonzalo
I have also seen that you changed killall for pkill π
Z
02:14
Zack
yes
G
02:14
Gonzalo
Let's hope that pkill is already on all systems
Z
02:15
Zack
yes, hopefully
02:15
if not, maybe ill write some code to look at the system to see which is available.
I want to avoid adding dependencies.
I want to avoid adding dependencies.
G
02:16
Gonzalo
Zack when c-mining to a full node on the same computer... is it safe to leave the pubkey thais defined at miner.erl? I guess that yes since all the blocks are credited to the full node
02:16
Deleted Account
In reply to this message
how..? i gave you commands to stop miner not update ur node
G
02:16
Deleted Account
key they are not lost if you followed my commands
G
Z
G
02:19
Gonzalo
I mean at "miner.erl". Do we have to change the pubkey if c-mining on a full node on the same computer?
Z
02:22
Zack
In reply to this message
I understand now. The mining pool pays out rewards, but the full node does not. So as long as you don't use a mining pool, you don't have to change the pubkey in miner.erl
G
02:22
Gonzalo
ok thanks
02:26
In reply to this message
means that one gpu miner already exists he just happened to find working one. what do you think..?
Z
02:27
Zack
Does it really take 1.6 Gigahash to mine a block?
MH
02:28
Mandel Hoff
Yes, current diff is 1,660,944,384.
02:28
Deleted Account
shoot
Z
02:29
Zack
so it would take my gpu 40 minutes to find a block, or my CPU would take 2 hours.
02:30
1.6 hours for my cpu.
MH
02:31
Mandel Hoff
There is no chance that was luck.
Z
02:35
Zack
The GPU software is very close to working.
I test each piece of it, and every piece looks functional. I am not sure why it is making bad work.
Maybe someone put it an hour of work to get it working, and they aren't sharing the result.
I test each piece of it, and every piece looks functional. I am not sure why it is making bad work.
Maybe someone put it an hour of work to get it working, and they aren't sharing the result.
MH
02:35
Mandel Hoff
I was observing ~60 seconds for block propagation during that GPU run. Anything anyone else mined would have been orphaned for sure. Dominant miner was getting 3x blocks before block even propagated.
02:41
Deleted Account
make sense
Z
02:44
Zack
we can get the gpu software working before launch, or we can pay this person to open source their work
02:44
We can keep the block reward small at launch, and increase it once the gpu code is available.
02:45
Deleted Account
how do you intend to pay him so far he is anonymous
Z
02:45
Zack
We can use an Amoveo smart contract to pay him.
MH
02:48
Mandel Hoff
I'm sure we can get it working before launch. I'm working on payment tx verification for the pool, and then I'll make some turbo miner tools.
G
02:49
Gonzalo
I have seen this querying peers:al().:
02:49
{{73,232,25,...},8080},
{{209,250,...},8080},
{{37,...},8180}]
02:49
??
Z
02:49
Zack
rp(peers:all()).
02:49
if you don't use
rp, then erlang will shorten the message so it fits on your screen better
G
02:50
Gonzalo
oh great, thanks
02:51
I'm counting 27 nodes right now!
Z
02:52
Zack
I only have 18 peers.
a lot of them don't have external ip available.
We aren't deleting them well enough.
a lot of them don't have external ip available.
We aren't deleting them well enough.
02:54
all the fake peers are slowing down block propagation
02:56
Now I only have 10 peers. I removed a lot of fake ones.
G
02:56
Gonzalo
Now I only see 8
03:03
Deleted Account
got this data
["mining_data"]
mining data block hash is no one to sync with
"pnyXrjx3wdLtunFbMKb1Es5iLZYNdQWhwz+Oxh2ZzyY="
got this data
["mining_data"]
mining data block hash is no one to sync with
"pnyXrjx3wdLtunFbMKb1Es5iLZYNdQWhwz+Oxh2ZzyY="
got this data
["mining_data"]
no one to sync with
mining data block hash is "CKr/Dny4zpcO+y473d+SXn+Wydp6OZnqQrg8Kv3V5/Q="
["mining_data"]
mining data block hash is no one to sync with
"pnyXrjx3wdLtunFbMKb1Es5iLZYNdQWhwz+Oxh2ZzyY="
got this data
["mining_data"]
mining data block hash is no one to sync with
"pnyXrjx3wdLtunFbMKb1Es5iLZYNdQWhwz+Oxh2ZzyY="
got this data
["mining_data"]
no one to sync with
mining data block hash is "CKr/Dny4zpcO+y473d+SXn+Wydp6OZnqQrg8Kv3V5/Q="
03:03
no one to sync with
03:04
what this suppose to mean
Nth joined group by link from Group
Z
03:09
Zack
In reply to this message
it means you have no peers.
I guess I made my blacklist too aggressive.
If you turn it on and off, then you will restart with the default list of peers.
I guess I made my blacklist too aggressive.
If you turn it on and off, then you will restart with the default list of peers.
03:13
Deleted Account
i have two peers now
03:14
(amoveo_core_prod@usman-GE70-2PC)1> rp(peers:all()).
[{{178,152,136,153},8080},{{159,89,106,253},8080}]
ok
[{{178,152,136,153},8080},{{159,89,106,253},8080}]
ok
Z
03:14
Zack
I think one is my server, and one is your own computer.
Z
03:22
Zack
I just did an update that should reduce the fake peers
D
03:46
David
how long does syncing take? it seems stuck for hours on block 0 on my vps
sync_mode:check().
quick
(ae_core_prod@ubuntu)44> api:height().
6182
(ae_core_prod@ubuntu)45> block:height().
0
(ae_core_prod@ubuntu)46> rp(peers:all()).
[{{203,80,236,230},8080},
{{169,231,8,73},8080},
{{199,247,25,21},8080},
{{209,250,250,137},8080},
{{159,65,182,117},8080},
{{162,218,209,18},8080},
{{159,65,44,147},8080},
{{159,65,134,21},8080},
{{24,5,185,238},8080},
{{51,15,69,135},8080},
{{178,152,171,191},8080},
{{159,203,4,195},8080},
{{58,152,135,108},8080},
{{37,211,237,126},8080},
{{52,234,133,196},8080},
{{64,137,240,136},8080},
{{181,120,161,194},8080},
{{59,149,207,33},8080},
{{37,211,192,130},8080},
{{37,228,235,74},8080},
{{178,152,136,153},8080},
{{51,15,212,91},8080},
{{73,95,148,9},8080},
{{199,247,26,222},8080},
{{176,9,84,75},8080},
{{73,232,25,43},8080},
{{159,89,106,253},8080},
{{209,250,248,93},8080},
{{37,228,235,74},8180}]
ok
sync_mode:check().
quick
(ae_core_prod@ubuntu)44> api:height().
6182
(ae_core_prod@ubuntu)45> block:height().
0
(ae_core_prod@ubuntu)46> rp(peers:all()).
[{{203,80,236,230},8080},
{{169,231,8,73},8080},
{{199,247,25,21},8080},
{{209,250,250,137},8080},
{{159,65,182,117},8080},
{{162,218,209,18},8080},
{{159,65,44,147},8080},
{{159,65,134,21},8080},
{{24,5,185,238},8080},
{{51,15,69,135},8080},
{{178,152,171,191},8080},
{{159,203,4,195},8080},
{{58,152,135,108},8080},
{{37,211,237,126},8080},
{{52,234,133,196},8080},
{{64,137,240,136},8080},
{{181,120,161,194},8080},
{{59,149,207,33},8080},
{{37,211,192,130},8080},
{{37,228,235,74},8080},
{{178,152,136,153},8080},
{{51,15,212,91},8080},
{{73,95,148,9},8080},
{{199,247,26,222},8080},
{{176,9,84,75},8080},
{{73,232,25,43},8080},
{{159,89,106,253},8080},
{{209,250,248,93},8080},
{{37,228,235,74},8180}]
ok
Z
03:48
Zack
In reply to this message
update to the newest version of the code. this is a problem that was fixed today.
D
03:48
David
ok
Z
04:03
Zack
My server is only keeping track of 5 peers now. I think it is working.
04:16
Now we don't have to manually do
sync_mode:normal(). after syncing. It happens automatically.
04:21
Now we don't have to manually do
sync_mode:quick(). when we start syncing. It is automatic.
KR
Z
04:55
Zack
I did another update. Now we check if a peer is valid before we add it to our list of peers.
MH
05:47
Mandel Hoff
I did a rough calc on that GPU miner's speed. That person was getting very close to 83mh/s for 20+ minutes. Looks like they stopped or didn't update their node yet. No recent action.
Z
05:47
Zack
so are we sure it is a gpu then?
MH
05:49
Mandel Hoff
83mh/s would be about twenty i7 quadcore CPUs, which are about 2mh/s. Almost certainly would be a Gpu.
05:50
Probably can start estimating rough initial difficulties for main net with that target.
Z
05:50
Zack
maybe someone rented a bunch of servers to mess with us? I doubt this would cost more than $2
05:52
Deleted Account
In reply to this message
Right. Docker container, some bash scripts, spin up 20 i7s. That is the simplest explanation.
Z
05:52
Zack
yeah, if like 30 people signed up for free trials
05:53
Can anyone help me with the GPU code? it is very near to complete.
MH
05:53
Mandel Hoff
Ok, I can't prove GPU, but 83mh/s is a pretty close approx to that address's speed.
Z
05:54
Zack
thanks for the estimate. it helps a lot
MH
05:56
Mandel Hoff
As long as my pool code doesn't blow up horribly, I'll be working on miner cpu and gpu code Friday until main launch (or done).
05:56
I wrote a bunch of code to monitor confirmed blocks and resend transactions that get lost. Needs testing. Not deployed yet.
05:58
I'll make some sort of dashboard for it too, so we can have an easy way to watch transactions. Probably will start with a simple table, but will add "search" someday.
05:58
The pool was easy - all the payout management is the hard part.
Z
06:00
Zack
I think the way to fix this is to make txs propagate better.
MH
06:03
Mandel Hoff
It's still good for my pool to confirm payouts. Otherwise, I could spend so much time hunting down "I didn't get my payout" claims. Now, I can find which block they were rolled in to.
Z
06:03
Zack
yes, it is important to be able to show the customer where the tx happened.
06:05
At some point we need to write a merkle proof library for the txs in the block, so customers could look up the tx by knowing the hash of the tx and the block it appeared in. And a light node could verify that the tx did appear in that block.
Because when you balance goes up, it is hard to know why it went up. Like if you are expecting 2 payments, it is hard to know which person paid you.
Because when you balance goes up, it is hard to know why it went up. Like if you are expecting 2 payments, it is hard to know which person paid you.
07:12
Deleted Account
What's left for the GPU miner to be ready? I can probably help
Deleted joined group by link from Group
Z
07:14
I can't figure out what is wrong. I keep testing the pieces, and they all do what I expect. But the work it outputs is invalid.
07:20
Deleted Account
sweet! Will check if i can figure it out
Z
07:20
Zack
great. thank you
07:21
https://github.com/zack-bitcoin/amoveo-c-miner
here it is in C. this one is working.
here it is in C. this one is working.
07:22
Deleted Account
π
MH
07:30
Mandel Hoff
Zack, might have a rounding error bug in the light wallet spend. I spent 210000000 with a fee of 152050, and the tx that ended up in the block was 209847949 with a fee of 152051. This is in block 6270.
Z
07:32
Zack
it is weird how the rounding error is the exact same size as the fee. I wonder what is going on.
MH
07:33
Mandel Hoff
No, I didn't mean it rounds off an amount of 152050. It looks like fee is taking an extra +1.
07:34
The 210000000 includes the 152050 amount.
Z
07:34
Zack
oh, they still add up to the correct amount, the problem is that one extra satoshi went with the fee instead of the tx
07:35
do i get it now
07:35
?
MH
07:35
Mandel Hoff
Also, I see your node's 0.7 payouts are using a 152118 fee. Did the governance value change, or is the fee code different for pool payouts than from light wallet fees?
07:35
Yes, that's right.
Z
07:36
Zack
I think I was too lazy to lookup the right number, so I just typed in a number that I felt was probably big enough, and then the test passed so I moved on.
07:36
so it is paying a higher fee than necessary
07:37
it is probably the miner fee that is too high, and the governance fee is being looked up.
07:37
since the miner fee is defined in the config file.
07:37
every miner could be different
07:38
if I hard-coded the governance fee, that would be a mistake.
MH
07:38
Mandel Hoff
Ok, sounds fine to me. Just wasn't sure if I needed to raise my tx fees or not. Wanted to make sure I wasn't using a fee that was invalid due to being too low.
Z
07:39
Zack
if you are running the mining pool, then any extra fee is just paying yourself.
07:39
unless you are publishing the tx for others
07:51
I updated the block syncing protocol.
Now it syncs blocks faster.
And when I rebooted the server, it didn't interrupt my laptop from syncing blocks.
You can optimize for your computer using a couple numbers in the config file.
Now it syncs blocks faster.
And when I rebooted the server, it didn't interrupt my laptop from syncing blocks.
You can optimize for your computer using a couple numbers in the config file.
MH
07:58
Mandel Hoff
Sounds great! π
Z
08:11
Zack
In reply to this message
Thinking more about this.
If you use a new account for every on-chain payment you receive, then you would know exactly which payment you received. So you don't need to look up txs in blocks.
If you use a new account for every on-chain payment you receive, then you would know exactly which payment you received. So you don't need to look up txs in blocks.
John joined group by link from Group
η΄’ε
η| ηζ¬θͺRealSatoshi joined group by link from Group
I
16:34
Iridescence
I'm syncing a fresh node, but I'm stuck at block 3379
17:10
Deleted Account
Is there another pool?
Z
17:17
Deleted Account
I just rebuilt my node and miner, since so many changes where pushed. I just couldn't get the node to start.. but no problem.. also backed up my node keys.db
17:19
what i did to mess it up, was try to restore my keys.db, but didn't do it correctly. .I'll need to test that to see the correct procedure so I don't loose fund at mainnet.
Z
17:31
Zack
keys.db go in _build/prod/rel/amoveo_core/keys/keys.db
you should be able to restore your keys after the update with this command:
you should be able to restore your keys after the update with this command:
cp _build/prod/rel/ae_core/keys/keys.db _build/prod/rel/amoveo_core/keys/keys.db
17:34
In reply to this message
I launched a fresh node with the newest code, and it did not get stuck while syncing. already on 3650
17:37
It synced all 6352 blocks on my first try. did not get stuck anywhere.
JΓΆrg LΓΌck joined group by link from Group
17:47
Deleted Account
yah.. it was my mistake.. i didn't copy the file, but copy and paste the contents, which didn't work
17:47
so scp my keys.db next time
Z
18:10
Zack
Now the block tells you how many VEO exist, and other useful info. This was @Mandelhoff 's idea.
https://github.com/zack-bitcoin/amoveo/blob/dev/apps/amoveo_core/src/records.hrl#L40
It would be a hard-fork change, so I haven't added it to the testnet yet.
https://github.com/zack-bitcoin/amoveo/blob/dev/apps/amoveo_core/src/records.hrl#L40
It would be a hard-fork change, so I haven't added it to the testnet yet.
MH
m
19:30
manu
It synced all blocks like a charm
Z
Deleted joined group by link from Group
23 February 2018
MH
03:24
Mandel Hoff
Zack - I think your node is down. Height is around 6404, and your node shows sub-6400.
Z
03:47
Zack
my cpu has been at 100% for 4 hours. looks like something went wrong.
03:49
looks like the new code for downloading blocks faster can occasionally get stuck in an infinite loop. I can fix this.
04:08
Deleted Account
Finally, able to get caught up with all the chat log. Guys, is it okay to run all 3 on the same server?
Z
04:08
Zack
yes, it should be fine to run all 3 at once on one server.
But it is unusual. Are you sure you need all 3?
But it is unusual. Are you sure you need all 3?
04:09
Deleted Account
Node, Pool, and Miner
04:10
Just testing the water. I may just connect to Mandel's or your pool on mainnet
Z
04:11
Zack
you can connect your miner directly to the full node. you don't need a pool.
04:16
The problem was the automatic switch from sync_mode:quick to sync_mode:normal.
So this step is once again manual. I updated the documentation to reflect this.
So this step is once again manual. I updated the documentation to reflect this.
04:18
Deleted Account
i left my computer for mining for a night yesterday and i stopped stopped my node at morning. Now i tried to get my node running with make prod-restart sync_mode:quick() sync:start().
04:19
c get_blocks
sync get_blocks
sync get_blocks
(amoveo_core_prod@usman-GE70-2PC)3> api:balance().
0
sync get_blocks
sync get_blocks
sync get_blocks
(amoveo_core_prod@usman-GE70-2PC)4> api:height().
6409
sync get_blocks
sync get_blocks
sync get_blocks
sync get_blocks
(amoveo_core_prod@usman-GE70-2PC)5> block:height().
0
sync get_blocks
sync get_blocks
sync get_blocks
sync get_blocks
sync get_blocks
(amoveo_core_prod@usman-GE70-2PC)3> api:balance().
0
sync get_blocks
sync get_blocks
sync get_blocks
(amoveo_core_prod@usman-GE70-2PC)4> api:height().
6409
sync get_blocks
sync get_blocks
sync get_blocks
sync get_blocks
(amoveo_core_prod@usman-GE70-2PC)5> block:height().
0
sync get_blocks
sync get_blocks
sync get_blocks
Z
04:19
Zack
Everyone needs to update. Like 1/2 the nodes on the network right now are frozen.
04:19
Unless you updated in the last 6 minutes, then you need to update.
04:20
Deleted Account
will try that.
Z
04:20
Zack
8 days until the launch
04:21
Deleted Account
after git pull
Z
04:21
Zack
cool
04:22
is it also syncing blocks?
Z
04:23
Zack
the new block sync is a lot faster, but it takes a bit to get going. lots of errors in the first few seconds.
04:23
Deleted Account
yes it seems like it is syncing . But i can't tell block numbers now
04:23
Deleted Account
Someone should publish list of available pools in case someone just wants to mine.
04:30
While mining with cminer, you can't see the hashrate?
Z
04:31
Zack
the readme has instructions on how to estimate your hash rate.
04:32
Deleted Account
You're talking about miner:speed_test(). ?
Z
04:32
Zack
i don't know. ill look at the readme and see
04:33
oh, looks like it does involve
miner:speed_test().
04:34
Deleted Account
hey guys can i mine from my laptop i cant afford a mine rig?
04:35
Deleted Account
0.3mh. Sucks. Lol
Z
04:36
Deleted Account
Zack how is the gpu miner going ?
Z
04:39
Deleted Account
It's a cheap VPS for 2.5/month
Z
04:39
Zack
my priorities are like this:
1) don't let the money get destroyed
2) don't let the network freeze
3) gpu miner
1) don't let the money get destroyed
2) don't let the network freeze
3) gpu miner
04:40
In reply to this message
like Tia says, a VPS might be better.
If GPU mining exists, then CPU mining wont be profitable.
I don't know the energy consumption of your laptop, or how much you pay for electricity.
If GPU mining exists, then CPU mining wont be profitable.
I don't know the energy consumption of your laptop, or how much you pay for electricity.
04:40
Neither do I know how much a VEO will be worth, and I also don't know how high the difficulty will be.
04:41
So trying to guess if you will make a profit is impossible for me.
04:41
Deleted Account
I think I am just going to mine in a pool if I want to get any veo
04:42
Deleted Account
what is the website to mine from laptop please
Z
04:43
Zack
The vast majority of users are better off buying instead of mining.
04:44
Deleted Account
yes how can we buy?
Z
04:45
Zack
In reply to this message
https://www.reddit.com/r/AmoveoTrader/
I made this reddit to help people who are buying and selling find each other.
I made this reddit to help people who are buying and selling find each other.
04:46
It will probably be a long time until Amoveo is on any exchange.
04:47
Deleted Account
Hey Zack, if you can get that GPU miner to work for my ATI cards I used for Dash back in 2014, then I may be able to get earn some veo
04:47
π
04:48
Deleted Account
zack what is address for lightwallet to mine wirh laptop please
04:48
Deleted Account
Or better yet, just tell me how many veo would 1 btc get me? Lol
04:48
Please check his GitHub. Quit making him retype the same answers
Z
04:49
Zack
In reply to this message
if you are the one who will profit, then maybe you could hire someone to get the GPU code working?
04:49
In reply to this message
http://159.89.106.253:8080/wallet.html
javascript mines slower than c-miner.
javascript mines slower than c-miner.
04:50
Deleted Account
ok thank you and best of luck with the launchπ it will br great
04:50
Deleted Account
In reply to this message
I doubt my 4 year old video cards would make any dent in the mining space if GPU is available. π
Z
04:53
Zack
Here is the starting place to answer almost any question about Amoveo https://github.com/zack-bitcoin/amoveo
04:55
Deleted Account
zack i just try to open wallet url but page doesnt load
Z
04:56
Zack
try again.
04:57
the node just finished syncing, so it should work fine now.
05:05
Deleted Account
its geat working now. will we use this one when you lannch Amoveo
MH
05:07
Mandel Hoff
The transaction browser is available here if you want to see where a tx went:
http://amoveopool.com/transaction
http://amoveopool.com/transaction
05:07
I add a "personal received' tx list to the wallet and miner too.
05:08
Deleted Account
Hey... is 0.3mh normal rate for vps 1 core?
Z
05:08
Zack
Very cool list of txs. Can I share on twitter?
05:09
Deleted Account
Your laptop is single core?
Z
05:10
Zack
It is 2 cores, and I get like 0.16 mh/s per core.
MH
05:10
Mandel Hoff
Yes, should be fair to show off. Let me know when it's down or not sync'ing, and I'll keep it alive best as I can.
05:11
Tia, I get about 2.2mh/s with 7 threads on the cpu miner, so that's like 0.3mh/s per thread.
05:11
Deleted Account
my node is still syncing lol
05:12
it stucks in between and when i try to write a command it start syncing again
Z
05:12
Zack
In reply to this message
I synced mine like 3 times since you started.
How many blocks did you get so far?
How many blocks did you get so far?
05:12
Deleted Account
syncing. use
syncing. use
(amoveo_core_prod@usman-GE70-2PC)11> api:height().
6409
syncing. use
syncing. use
syncing. use
syncing. use
syncing. use
(amoveo_core_prod@usman-GE70-2PC)12> api:block().
** exception error: undefined function api:block/0
syncing. use
syncing. use
syncing. use
syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.(amoveo_core_prod@usman-GE70-2PC)11> api:height().
6409
syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.(amoveo_core_prod@usman-GE70-2PC)12> api:block().
** exception error: undefined function api:block/0
syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.syncing. use
sync:stop(). if you want to stop syncing.
Z
05:13
Zack
I am on 6410. so it looks like you are synced.
05:14
Deleted Account
no my balance was zero
05:14
i think i need to do prod-clean again
Z
05:14
Zack
the keys.db file changed location recently. if you copy it to the new location, then you will get your money back.
Check if your pubkey is the same.
Check if your pubkey is the same.
05:15
we renamed the files from
ae_core to amoveo_core
05:15
Deleted Account
us Amoveo still on test net
Z
05:16
Zack
In reply to this message
https://github.com/zack-bitcoin/amoveo
As you can see on this page
Amoveo main net will launch at 11:00 AM GMT on March 2, 2018.
As you can see on this page
Amoveo main net will launch at 11:00 AM GMT on March 2, 2018.
05:16
Deleted Account
it only changed once that was yesterday. Now it is same.
05:16
Deleted Account
ah ok
Z
05:17
Deleted Account
BFa/YmAlUiVmx6O3Md/xeAQ7Px4EFTxOWitlD3tqycDBGoyvDI58TYOVmH9WmvUyKqUnoCXE6HxenLjcXg6IDNo=
Z
05:18
Zack
my node says you have about 3 Veo.
05:18
does yours say something different?
05:19
Deleted Account
In reply to this message
i mined 3 veo before going to sleep. It did find many blocks when i checked in the morning on node. looks like something went wrong last night
Z
05:20
Zack
yes. My node died last night too. Hopefully the changes I made today fix this.
05:22
Deleted Account
well time to see how fast it syncs now
05:23
woah call it a flash update. Its going fast and i thought you removed the script for block numbers but turns out my node really was broken.
M
05:45
Mike
Is Amoveo the only project right now with functioning light nodes in browser? Finally tried it out. Itβs very impressive
Z
05:48
It looks like ethereum has tools to store your private key in the browser, but I can't find anything about verifying headers.
So maybe we are first.
So maybe we are first.
Z
06:10
Zack
I did an upgrade to prevent your node from trying to sync with multiple peers simultaneous.
This should reduce bandwidth consumption, and it might fix whatever caused all the nodes to freeze recently.
This should reduce bandwidth consumption, and it might fix whatever caused all the nodes to freeze recently.
Z
06:26
Zack
There was a problem with block propagation that I fixed.
Everyone was sharing new blocks to the nodes in the same order, so peers on the bottom of the list weren't finding out about new blocks.
I randomized the order to fix this.
Everyone was sharing new blocks to the nodes in the same order, so peers on the bottom of the list weren't finding out about new blocks.
I randomized the order to fix this.
06:28
In reply to this message
https://status.im/
This looks like a light-node phone app for ethereum.
This looks like a light-node phone app for ethereum.
MH
G
07:07
Gonzalo
Great!
MH
07:07
Mandel Hoff
The tool exe and dlls can be downloaded here after entering a valid miner address:
http://amoveopool.com/miner
http://amoveopool.com/miner
07:07
Building it might be a pain for most people. Visual Studio, Boost, and RestCPP are build requirements.
G
Z
MH
07:11
Mandel Hoff
In reply to this message
Yes, exactly this is in the download zip at amoveopool.com/miner
G
MH
07:12
Mandel Hoff
I'd rather host the release zip on github. I'll have to see if they have a release zip hosting thing or not. I thought I've seen projects with release downloads on github but maybe that's a paid thing.
Z
07:13
Zack
I want to put a link to the miner in the amoveo github. Which URL is best?
Should I link to your github?
Should I link to your github?
MH
07:16
Mandel Hoff
Your call. The code is on github but the binaries are not there. Depends if you think people will want to view code or just download and run it.
Z
07:16
Zack
In reply to this message
It is next to the bright green button that say "Clone or Download". I think you want to click the button that says "upload files".
07:17
If people are downloading binaries, then they can't be certain whether the compiled code was actually built from the code you host on github.
MH
Z
07:20
Zack
great
07:23
Could anyone else try using Mandel's miner to confirm that it works?
I don't have a windows computer.
I don't have a windows computer.
G
07:26
Gonzalo
I'm mining with it right now
MH
07:26
Mandel Hoff
π
Z
07:27
Zack
awesome, thanks Gonzalo
G
07:28
Gonzalo
π
Z
07:30
Zack
I like how you can type all the info into the command line with your miner.
I think I should copy the same format for the linux c-miner
I think I should copy the same format for the linux c-miner
07:31
opening an erlang shell for mining is so awkward
KS
07:40
K Sq
Excitedddd
07:40
Hope some of you miners will sell OTC
07:40
Please pin the mainnet launch post for newcomers
G
07:42
Gonzalo
Zack is OK this new syncing message? "syncing. use sync:stop ..."
Z
07:44
Zack
In reply to this message
yeah, it is fine. maybe it was a mistake on my part to use this message. I wanted us to be more aware of how much syncing was happening for a while.
G
07:49
Gonzalo
thnaaks
07:51
I believe that someone is fast mining with a GPU with an old version of the node
Z
07:52
Zack
cool hypothesis. why do you think so?
07:52
blocks are coming really fast
07:52
so a gpu sounds possible
07:53
but why do you think they are using an old version of the code?
G
07:53
Gonzalo
I mantain 2 nodes, one is updated, nor the other... one is at height 6475, the other at 6534
Z
07:54
Zack
my node with new code is at 6534
G
07:54
Gonzalo
I've seen a burst of blocks in seconds, but on the outdated node
Z
07:54
Zack
when did you last update? a lot changed today
G
07:55
Gonzalo
less than 1 hour ago
Z
07:56
Zack
I guess something is still broken
07:57
do you have peers?
one mode it can get stuck in is if there is no one it knows to talk to.
peers:all().one mode it can get stuck in is if there is no one it knows to talk to.
07:57
is it spamming messages? or is it quiet?
07:57
is the CPU maxed out?
G
07:58
Gonzalo
wait... I did git pull and make prod-build, but NOT make prod-restart, so I did not delete the blockchain. Maybe this makes a difference, don't know
07:59
I've got 11 peers
07:59
is spamming "syncing. use sync:stop..."
07:59
CPU is at 100% but because I'm mining
Z
08:00
Zack
yes, I think you are right. The database got broken with the old code, and merely updating the code didn't fix your database.
08:00
Deleted Account
Prod-restart does not delete blockchain ?
08:01
Isnt prod-clean the only command to delete blockchain ?
Z
08:02
Zack
yes, Usman is correct.
08:02
In reply to this message
prod-restart doesn't fix your problem. you need
make prod-clean like Usman said.
G
08:02
Gonzalo
I think that restart implies clean + build + go + attach
08:03
So I was wrong
G
08:04
Gonzalo
Maybe it's not enought clear at https://github.com/zack-bitcoin/amoveo/blob/master/docs/getting-started/turn_it_on.md
Z
08:07
Zack
good idea. I will update that doc to be more clear
08:19
https://github.com/zack-bitcoin/amoveo/
Main net March 2 at 11:00 AM GMT
Main net March 2 at 11:00 AM GMT
Zack pinned this message
08:38
Deleted Account
So let me guess, we shut down our nodes, do a git pull then restart on launch date time?
Z
08:44
Zack
yes. you will need to delete the old blocks too
G
09:22
Gonzalo
wow another block burst
09:23
lots in just seconds
MH
10:19
Mandel Hoff
Yes, someone was getting 10-15 second blocks for 15+ minutes strait.
10:20
Nice to have a block tracker page.
10:20
Z
10:26
Zack
yes, the tracker page is great.
The difficulty has sure been going up fast.
The difficulty has sure been going up fast.
I
10:26
Iridescence
How is the block difficulty calculated?
Z
10:27
Zack
same as bitcoin.
MH
10:27
Mandel Hoff
Every 2k blocks, it recalculates to attempt to average 10 minute per block based on speed of the previous 2k blocks.
Z
10:28
Zack
yes
I
10:29
Iridescence
I see
10:29
Is that the target of Amoveo as well, 10 minutes per block?
Z
10:30
Zack
the target is one of the governance variables. the community decides.
10:30
it starts as 10 minutes.
10:42
It isn't good to invite too many people. We want Amoveo to grow slowly and smoothly. That way it is less likely to break.
10:47
Deleted Account
Isn't shorter block time with reduced rewards is better than longer block time with higher rewards?
Z
10:48
Zack
In reply to this message
There are many trade-offs. It is hard to know what is best. Probably what is best will change over time.
10:48
Deleted Account
Shorter block time means faster confirms no?
10:49
It depends how soon you want the confirmations I guess.
Z
10:49
Zack
Faster confirmations isn't so important in Amoveo because we have smart contracts inside of turing complete state channels.
So users will only rarely do transactions on-chain.
So users will only rarely do transactions on-chain.
10:50
6 confirmations with 10-minute blocks is just as secure as 30 confirmations with 2-minute blocks.
Takes 60 minutes either way.
Takes 60 minutes either way.
10:51
Deleted Account
Lol. True. I'd trust 30 confirms than 6. Lol
Z
11:05
Zack
The amount of time it takes to process the most expensive block and propagate blocks to the network needs to be less than 1/10th of the block period.
If it takes longer than this, then miners wont know what to mine on for too much of the time, and it becomes a way to centralize mining.
Or they will mine empty blocks, because they can't tell which txs are valid for including.
Right now block propagation is like 60 seconds, so it is already half broken. If we made the block period any shorter, it would be completely broken.
Eventually once the propagation is faster, we can consider smaller more frequent blocks.
If it takes longer than this, then miners wont know what to mine on for too much of the time, and it becomes a way to centralize mining.
Or they will mine empty blocks, because they can't tell which txs are valid for including.
Right now block propagation is like 60 seconds, so it is already half broken. If we made the block period any shorter, it would be completely broken.
Eventually once the propagation is faster, we can consider smaller more frequent blocks.
Nick Harris joined group by link from Group
11:38
Deleted Account
Zack is there a place to just get big announcements like required "git pull" or another network announcements?
11:39
once mainNet is launched it would be nice to have a notification, so I don't go half a day with a frozen node, simply because I didn't see a comment about a required "git pull" and restart
11:41
just a thought, even a email announcement would be fine. even a email subscription.. although I do get github emails, but I haven't seen anything in the github notifications that have said.. immediate git pull required or anything like that.. so not sure what you have planned for that in production
11:42
Deleted Account
I think this group is sufficient?
11:55
Deleted Account
ζΉδΎΏηθ―η¨θ±ζ
Z
12:00
Zack
In reply to this message
δ½ η°ε¨ε―δ»₯ε¨ζ΅θ―ιΎδΈζζγζ们ε°ε―ε¨δΈ»ιΎ3ζ2ζ₯γ
12:04
In reply to this message
Yes. This is good advice.
We need a disaster response notification system.
Maybe a different telegram group?
I will think more about which communication system is best.
We need a disaster response notification system.
Maybe a different telegram group?
I will think more about which communication system is best.
12:09
In reply to this message
For now this is a multi-lingual group. Once the different languages become distracting, we will split.
12:18
Deleted Account
ok, if u ever need any English to Chinese translations done, just hit me up
Z
12:19
Zack
In reply to this message
Awesome. Thank you.
There is a Chinese version of the white paper, but it isn't very good.
If you made it better, that would be great.
There is a Chinese version of the white paper, but it isn't very good.
If you made it better, that would be great.
12:19
Deleted Account
ill look into it
12:23
Deleted Account
I'm running a mining pool also.. 128.199.97.207:8085 if a list is being published.. also i reset my node, and mining pool and then at first block mined i found the key wasn't unlocked.. maybe there should be a warning when you run "sh start.sh" to start the mining pool that the wallet is locked.. I put a note to check "keys:status()." when I restart my node
12:28
also is there a command to check a public address balance from the node ?
12:35
not the node public address but other public addresses
Dylan Field joined group by link from Group
Deleted joined group by link from Group
m
16:23
manu
@zack with the new modifications always "node is not running" when prod-attach
G
m
G
16:39
Gonzalo
ops
Z
G
16:41
Gonzalo
I will try a git pull as well, let's see what happens to me
Z
m
16:41
manu
Ubunto 17.10
16:41
Git pull right now
Z
16:41
Zack
How about
make prod-restart ?
m
16:42
manu
Yup
Z
16:42
Zack
That fixed it?
m
16:43
manu
Not at all
16:43
I removed the directory
16:44
And try it again
Z
16:44
Zack
Did you install the dependencies like it says in the installation instructions?
m
16:44
manu
A few days ago
16:45
New dependencies now?
Z
16:46
Zack
No the dependencies haven't changed recently.
I have only used Ubuntu 16.04
So maybe 17.10 is different
I have only used Ubuntu 16.04
So maybe 17.10 is different
m
16:48
manu
Last days on 17.10 ran ok... i'll see what happens
Z
16:48
Zack
The browser light node is a lot easier to use than the full node. You don't have to install anything. Just visit a web page
m
16:48
manu
Ok
16:50
Deleted Account
got this data
["mining_data"]
mining data block hash is "bFGCBTazZ01/9ylNeCYOWzloLW8LdwfdbLP5gLVfd1c="
got this data
["mining_data"]
mining data block hash is "bFGCBTazZ01/9ylNeCYOWzloLW8LdwfdbLP5gLVfd1c="
(amoveo_core_prod@usman-GE70-2PC)16> api:balance().
6715248664
(amoveo_core_prod@usman-GE70-2PC)17> api:height().
6497
(amoveo_core_prod@usman-GE70-2PC)18> block:height().
6497
(amoveo_core_prod@usman-GE70-2PC)19>
While my actual balance is 13 and height 4827
["mining_data"]
mining data block hash is "bFGCBTazZ01/9ylNeCYOWzloLW8LdwfdbLP5gLVfd1c="
got this data
["mining_data"]
mining data block hash is "bFGCBTazZ01/9ylNeCYOWzloLW8LdwfdbLP5gLVfd1c="
(amoveo_core_prod@usman-GE70-2PC)16> api:balance().
6715248664
(amoveo_core_prod@usman-GE70-2PC)17> api:height().
6497
(amoveo_core_prod@usman-GE70-2PC)18> block:height().
6497
(amoveo_core_prod@usman-GE70-2PC)19>
While my actual balance is 13 and height 4827
G
16:50
Gonzalo
Zack on one node I'm getting "block absorber died!" and is not updating height. Node is updated. Any idea?
Z
17:03
Zack
In reply to this message
Why do you say "actual height is 4827"?
block:height is your actual height.
block:height is your actual height.
m
17:03
manu
It's working again maybe a stuck background process
Z
17:04
Zack
In reply to this message
cool.
sh scripts/kill_all_erlang.sh can be helpful in that situation.
lijun wang joined group by link from Group
m
17:04
manu
Yesss that was
lw
17:07
web
17:07
when Light Wallet-Amoveo mining
Z
17:08
Zack
hi lijun wang. Are you trying to explain a problem you have with using Amoveo?
17:08
Why did you share an ip address?
lw
Z
G
lw
Z
17:16
Zack
great
MF
17:17
Mr Fox
2018-03-02 main net ?
Z
17:17
Zack
yes
17:17
1 week, 1 hour, 40 minutes
MF
17:17
Mr Fox
cool
MH
MF
17:26
Mr Fox
17:27
what is the pool fee after the main net launched?
17:29
whatβs the Total Supply of amove?
MH
17:29
Mandel Hoff
I haven't decided. I'm pretty sure it'll be 10% or less. Yes, 30% is very high.
MF
17:30
Mr Fox
ok
MH
17:30
Mandel Hoff
There's no total supply, but veo can be destroyed. Veo per block is a governance variable that the community can change.
Z
17:30
Zack
In reply to this message
right now the fee is 1/650 of a block reward. and a block can fit about 650 txs.
17:30
I thought this is ok to start
MH
17:31
Mandel Hoff
Zack, do you ever sleep?
MF
17:31
Mr Fox
maybe not
Z
17:32
Zack
I am feeling pretty excited about the launch.
MH
17:32
Mandel Hoff
Same here.
MF
17:32
Mr Fox
you need have a rest
17:32
Sticker
Not included, change data exporting settings to download.
π, 15.6 KB
MH
17:32
Mandel Hoff
Zack's sleeping hours are also a governance variable.
MF
17:32
Mr Fox
lol
G
17:33
Gonzalo
In reply to this message
Compared with other coins pools 10% is still pretty high BUT this is just supply/demand
MF
17:33
Mr Fox
let us make it be 8 hours
17:33
Sticker
Not included, change data exporting settings to download.
π, 15.8 KB
MH
17:36
Mandel Hoff
In reply to this message
Yes, you're completely correct. The default github node/pool currently takes 30% unless you run a private one, and it doesn't have "shares" - so, unless you are multi-gpu at launch solo mining is going to be hard to earn any veo per day. I'm expecting a shared pool is going to seem like a valuable thing.
Z
17:37
Zack
mining pools are not so easy.
The one I made is only useful in that miner don't have to install erlang or run a full node.
The one I made is only useful in that miner don't have to install erlang or run a full node.
MH
17:37
Mandel Hoff
Single gpu is 10-15 seconds blocktime now. I'm expecting launch difficulty should be about 6,000 times larger than it currently is. That's 100 gpu with 10min block time roughly.
17:38
With difficulty at 6k times larger than now, shared credit is hopefully very good for everyone.
G
17:39
Gonzalo
In reply to this message
Yes, we also need shared pools, even at 10% fee, if we want to incentive people to maintain CPU nodes
Z
17:39
Zack
so you think we should start with a difficulty about 10892
MH
17:43
Mandel Hoff
30% higher - around 11042, which is 9,965,666,304,000 - which is 100x GPU targeting 10 min block
17:43
Of course, I have no idea of 100x gpu makes any sense
17:44
That could be high or low. I don't know what other people have for hardware.
17:44
That's based on that one miner's approx hash speed estimation, which was round 85-95 mh/s.
MF
17:45
Mr Fox
why 10 min? itβs too slow for waiting to be confirmed
MH
17:46
Mandel Hoff
Network propagation demands some confirmation. 10 min seems fine. Amoveo has channel lightning payments that don't require confirmation, so use that if block confirmation is unwanted.
17:46
Zack's Light node can do that, but my pool UI doesn't have that yet.
MF
17:49
Mr Fox
when one day veo be listed on exchanges, we can do anyting but wait for some confirms
17:50
Deleted Account
gpu miner finished?
MF
17:50
Mr Fox
it will be slow
Z
17:50
Zack
wikipedia says the best gpu can only do 8 gh/s on amoveo, and that would be with ideal software. mine is slower by a factor of 4.
https://en.bitcoin.it/wiki/Non-specialized_hardware_comparison
it would take someone with the ideal mining gpu 5000 seconds at the difficulty you suggest. so they would find a block every 1 hour 40 minutes.
https://en.bitcoin.it/wiki/Non-specialized_hardware_comparison
it would take someone with the ideal mining gpu 5000 seconds at the difficulty you suggest. so they would find a block every 1 hour 40 minutes.
MH
17:50
Mandel Hoff
Depends. Exchanges would probably use channels for lightning payments. That's instant.
Z
17:51
Zack
In reply to this message
the network decides. it starts as 10 minutes, but they will change it later.
MH
17:53
Mandel Hoff
In reply to this message
Sounds right - how many users with how many GPUs is harder to guess at. You did that twitter pool, but I have no evidence.
17:56
9,965,666,304,000 divided by 8gh/s is ~1245, which is 1 block per 20 minutes with a single gpu.
17:56
Might need to go higher. Not sure what sort of gpu that is though. Sounds pretty high end.
17:57
Based on people in this channel asking for gpu miners, I'd guess there will be at least 100 gpu running on day 1
Z
18:01
Zack
there is still no gpu software
G
18:35
Gonzalo
Zack I believe there's some block propagation problem... I own 2 nodes, both updated, both running c-miner as well, but they aren't updating block height. Your node at 159.89.106.253 says 6829, mine at 51.15.69.135 says 6828, the other at 51.15.212.91 says 6827. Many minutes have passed.
18:37
Also, noone of my two wallet.html will get the balance of an address
18:38
BNEXTy+F5hB2Oot2eV2t8+xULp9bVChnbPYUxYTbFbJvJBHlWGTwvTBeoYuagMe3J/IvjSFaMCjRVO/GID8NSHM=
Z
18:39
so it probably isn't a propagation problem. otherwise it would tell my address
18:39
oh, maybe this happens if you download headers without blocks
18:40
so it could be a propagation problem. you are right
G
18:41
Gonzalo
Let me know if there's something I can try/check
G
MH
18:43
Mandel Hoff
AmoveoMinerCpu.exe {YourAddress} {Optional-Threads} {Optional-PoolUrl}
G
18:43
Gonzalo
AmoveoMinerCpu.exe YOUR_ADDRESS CORES
MH
18:43
Mandel Hoff
Default threads is 4. Suggested using the default poolUrl too.
Z
18:44
Deleted Account
Thanks i downloaded the release from git hub it didn't have instructions.
G
18:45
Gonzalo
So 3 people answering a question that's already anwered... RTFM! ;-)
MH
18:46
Mandel Hoff
I should put the read me in the release zip. It's not there.
G
18:46
Gonzalo
Amoveo Cryptocurrency Miner for Cpu work to be used with http://AmoveoPool.com
Usage Template:
AmoveoMinerCpu.exe {WalletAddress} {Threads} {PoolUrl}
Threads is optional and defaults to 4.
PoolUrl is optional and defaults to http://amoveopool.com/work
18:47
It's on GitHub and on the exe as well... Should be enought...
MH
G
18:50
Gonzalo
Better for sure π
18:51
Mandel:
H/S: 1502289 S:0 S/Hr:0
H/S: 1502271 S:0 S/Hr:0
ERROR: GetWork: 500 Sleep and retry...
ERROR: GetWork: 500 Sleep and retry...
ERROR: GetWork: 500 Sleep and retry...
ERROR: GetWork: 500 Sleep and retry...
ERROR: GetWork: 500 Sleep and retry...
ERROR: GetWork: 500 Sleep and retry...
Z
G
18:52
Gonzalo
I stoped minutes before with Ctrl+C (was mining with 1 core) and restarted with 2 just to have a try...
Z
18:52
Zack
Hopefully someone here will test it before I make wider announcements
MH
18:53
Mandel Hoff
Node probably froze or something.
G
18:53
Gonzalo
ok
18:55
In reply to this message
I'll test it later, I'm pretty busy at work right now (and at the moment I need some FIAT as well π)
Z
18:55
Zack
In reply to this message
ok, no worries. You have been plenty helpful Gonzalo, I am sure someone else will be able to test the gpu miner.
G
18:56
Gonzalo
thanks, I'm glad to help π
Z
18:56
Zack
my gpu isn't very good. I mine slow even with the new software.
MH
19:01
Mandel Hoff
Ok, I think my pool node is online again.
G
MH
19:02
Mandel Hoff
Probably need to run multiple nodes have my pool do fail over when one goes down. Fun.
Z
19:09
Zack
The new miner seems to be 3x faster, but it is still maxing out my CPU.
Maybe I have it configured wrong?
Maybe I have it configured wrong?
19:09
or maybe I programmed it poorly
MH
19:14
Mandel Hoff
Reading the code. Looks great. I don't have ubuntu with a gpu to test it. I might take a swing a windows version in the next few days.
Z
19:14
Zack
I am testing with mac osx
19:15
Deleted Account
is the gpu miner for nvidia or amd..?
Z
19:15
Zack
I am curious about what happens if you try to run on a computer without a GPU. maybe I wrote it wrong and it is compiling for CPU.
19:15
Deleted Account
usman@usman-GE70-2PC:~/Downloads/amoveo-opencl-miner$ sh compile.sh
gcc: error: OpenCL: No such file or directory
gcc: error: unrecognized command line option β-frameworkβ
miner.erl:104: Warning: variable 'E' is unused
miner.erl:115: Warning: no clause will ever match
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
gcc: error: OpenCL: No such file or directory
gcc: error: unrecognized command line option β-frameworkβ
miner.erl:104: Warning: variable 'E' is unused
miner.erl:115: Warning: no clause will ever match
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
Z
19:15
Zack
This is my first time writing code for the GPU, so I am unsure of a lot of things
19:16
looks like opencl isn't installed for you
19:16
I think it came pre-installed with Mac OSX, or it came with dev tools or something
19:17
If someone manages to get this to run in Linux, please share the details of how you did it.
I think I have never connected a GPU to a linux computer before.
I think I have never connected a GPU to a linux computer before.
Z
19:52
Zack
I changed a compiler setting, and now it is like 20 times faster and isn't using CPU.
G
19:52
Gonzalo
ππ
MH
19:53
Mandel Hoff
Great job
Z
19:54
Zack
I don't think so.
I made the job 100 times bigger, and it isn't taking any longer.
I think it isn't actually mining.
I made the job 100 times bigger, and it isn't taking any longer.
I think it isn't actually mining.
20:01
speed test shows that I am getting 0.58 mh/s
Which is only twice as fast as the miner in C.
I think it is not using the GPU to miner.
Which is only twice as fast as the miner in C.
I think it is not using the GPU to miner.
G
20:02
Gonzalo
Wow... maybe you have improved the CPU miner ;-)
20:05
Deleted Account
He already said miner is not using cpu
Z
20:07
Zack
Wikipedia says I can get like 3.8 mh/s at best from my gpu.
I am getting 0.6.
maybe it is just poorly written gpu code
I am getting 0.6.
maybe it is just poorly written gpu code
20:07
I am not sure if it is using the gpu
G
20:33
Deleted Account
The c miner would crash from time to time. Anyone has the same problem?
Z
20:33
also, when the mining pool crashes.
20:34
Deleted Account
Ok. Thanks.
20:36
Is there a way to check my hashrate?
Z
20:37
Zack
yes. look at the readme
Z
21:57
Zack
I think the problem is that I programmed the miner in a linear way, and my OpenCL implementation is smart enough to use CPU or GPU depending on the situation.
So if I fix the software to be parallelizable, then the compiler will use the GPU more.
So if I fix the software to be parallelizable, then the compiler will use the GPU more.
Z
22:17
Zack
It turns out that the CPU wasn't doing any computation. It was just frozen waiting for the GPU to return.
22:18
i can insert a sleep statement to fix this on my machine, but it seems like every GPU will need to sleep a different amount of time. So I can't hard-code it. It needs to be calculated from a test.
22:23
no, I was wrong. that isn't why cpu is being wasted.
22:23
So I am back to thinking it is because I programmed in a single-threaded way.
Marco joined group by link from Group
MH
23:09
Mandel Hoff
Got my pool miner working on Ubuntu!
23:09
23:11
New Windows release too:
https://github.com/Mandelhoff/AmoveoMinerCpu/releases
Runs faster on Windows. I went from 2.2mh/s on 7 threads to 3.5mh/s on 7 threads.
https://github.com/Mandelhoff/AmoveoMinerCpu/releases
Runs faster on Windows. I went from 2.2mh/s on 7 threads to 3.5mh/s on 7 threads.
23:27
how many mh/s does it show..?
23:33
Deleted Account
i now have 2 servers running miners, and a node with mining pool.. but no blocks are getting mined....
23:34
I'm not talking just about me.. but for the network
23:38
Deleted Account
ok never mind.. both of my server found a block about the same time..
MH
23:40
In reply to this message
Count hashes attempted with unique nonces and divide by elapsed time.
23:41
Deleted Account
that is twice as fast from ubuntu miner
MH
23:41
Mandel Hoff
Is your screenshot using my new ubuntu miner?
23:41
Deleted Account
no its windows miner
23:42
new release
23:42
AmoveoMinerCpu x64 Windows v1.0.0.1
23:42
and its working i found a block on your pool already
MH
23:43
Mandel Hoff
Yes, it's pretty fast. I had custom sha256 code that turned out to be slower than openssl's library. Making it linux compatible forced me to figure that out.
23:45
I updated my ReadMe.md for Windows and Linux directions. It's much better than it used to be.
23:51
there isn't any windows version of amoveo pool software available yet right.?
MH
23:56
Mandel Hoff
No, pretty sure that'll stay Ubuntu/Erlang a long time.
23:58
Zack - I think your node is not syncing. You're ~30 blocks behind my node.
24 February 2018
00:01
Deleted Account
my node is synch up with the light wallet node
RL
00:02
R L
In reply to this message
Mandel thanks for nailing this. Your site/pool rocks. Great work.
MH
00:02
Mandel Hoff
Thank you.
I
00:08
Iridescence
Zack, do you need a more powerful rig?
MH
00:09
Mandel Hoff
I'm running my full node and pool service on the smallest ubuntu (1cpu) that Azure offers. It's very low profile. The badwidth consumption is very reasonable now.
G
00:14
Gonzalo
In reply to this message
I'm at the same height than Zacks. I still believing we have some block height propagation problem. To update the node I have to do a prod-clean and prod-restart... then will update and get stuck again
00:21
Deleted Account
i just resynched to 6978
00:24
restarting everything again.. seems like I wasn't actually synching with network..
00:25
the light wallet is 50 blocks behind my node now
00:25
6979
00:25
vs. 6928
G
00:26
Deleted Account
no.. actually never thought about that.. using commandline
G
00:27
Gonzalo
localhost:8081/wallet.html
00:28
Deleted Account
thanks... not sure who's node I was using but it's way behind
G
00:29
Gonzalo
sorry, localhost:8080/wallet.html
00:29
hehe ok
00:31
Deleted Account
also. I was having a big problem with my node messing up when I closed my terminal so trying tmux to keep the session active when I close my remote terminal
G
00:32
Gonzalo
so tmux does it?
I
00:32
Iridescence
Yes tmux enables you to keep running a session even though you close the connection
G
00:33
Gonzalo
nice to know, also for my work, thanks
00:33
Deleted Account
yes.. i've been doing backend server admin for fun, and just learned that
00:33
good to know
00:36
sucks.. i mined 2 blocks, but resynched and lost them
00:36
not part of consensus :(
00:38
i was mining too far behind everyone else :(
G
00:38
Gonzalo
Yeah, I also sent VEO when not on the top height and also I think I lost them
00:39
Deleted Account
i keep needing to start from 0
00:39
hope tmux will help.. i think my node just pauses when i exit, so checking it out now to keep it going
00:40
I can have a remote session going all the time
00:41
i'm new, but i find it hard to know for sure if I'm at the top height
00:44
6994
00:44
I mined at least one block.. not sure if anyone is accepting them though
00:46
i only have 3 peers
00:50
looks like my node is trying to synch, and give blocks but many peers aren't accepting my blocks
00:50
I guess due to me being behind before
00:50
I'm not trusted :(
00:51
7000
00:55
i guess I'll just try to exit with tmux, and let it run this afternoon.. and see if I get any credit for blocks mined.. I'm mining, but they don't added to consensus
G
00:55
Gonzalo
Ok, so it's seems that the only node that is up to date is Mandel's... the others are kaputt:
00:55
(6168) 199.247.25.21:8080/wallet.html
(0) 162.218.209.18:8080/wallet.html
(6829) 159.65.182.117:8080/wallet.html
(7003) 52.234.133.196:8080/wallet.html (Mandel?)
(6994) 51.15.212.91:8080/wallet.html (Gonzalo)
(6976) 51.15.69.135:8080/wallet.html (Gonzalo)
(broken) 176.9.84.75:8080/wallet.html
(6437) 199.247.26.222:8080/wallet.html
(6976) 159.89.106.253:8080/wallet.html (Zack)
(6385) 209.250.248.93:8080/wallet.html
(0) 162.218.209.18:8080/wallet.html
(6829) 159.65.182.117:8080/wallet.html
(7003) 52.234.133.196:8080/wallet.html (Mandel?)
(6994) 51.15.212.91:8080/wallet.html (Gonzalo)
(6976) 51.15.69.135:8080/wallet.html (Gonzalo)
(broken) 176.9.84.75:8080/wallet.html
(6437) 199.247.26.222:8080/wallet.html
(6976) 159.89.106.253:8080/wallet.html (Zack)
(6385) 209.250.248.93:8080/wallet.html
00:56
at 7002
00:57
7006 now
G
00:57
Gonzalo
yes, tell me in 15 minutes time please <-- dont tell me, I will look ;-)
01:00
just to try something different I did a "sh scripts/kill_all_erlang.sh", then clean, then restart. Now it seems that is syncing properly
Z
01:12
Zack
In reply to this message
You don't need tmux.
Use ctrl D to make it a background process.
You can reattach with
Use ctrl D to make it a background process.
You can reattach with
make prod-attach
01:15
Deleted Account
thanks
Z
01:16
Deleted Account
I never used screen, but tmux seemed to work fine..
01:17
closed tmux..session and closed terminal windows, and then found a block no problem.. I'll try ctrl + d next time
01:18
i'm going to let my node run and mine this afternoon and with luck I'll keep those coins this time
s
01:24
scott_l | DeFi Pulse
if anyone needs monies/support to build on amoveo, please let me know.
G
MH
01:27
Mandel Hoff
Ha! You jinxed me. My node just died hard. Working on it now.
G
01:29
Gonzalo
In reply to this message
Remember to do
sh scripts/kill_all_erlang.shafter halting the node, It seems that it makes a difference
01:30
Now only Scott's node and mines are up-to-date.
MH
01:30
Mandel Hoff
Are you over 7k?
G
01:30
Gonzalo
Scott, we are saving the testnet!! ππ
01:30
Deleted Account
i saw that nice
G
01:30
Gonzalo
Yes Mandel, 7010
01:30
Deleted Account
once i figure this out, I'll have to run 2 nodes
01:31
for main net
MH
01:31
Mandel Hoff
Nice. I'm back at 6833 for some reason after restart.
Z
01:31
Zack
In reply to this message
I don't think you need to do this. This command might turn off other programs on your system.
You can use
You can use
top to see if you have any zombie beam processes.
G
01:31
Gonzalo
(7010) 51.15.212.91:8080/wallet.html (Gonzalo)
(7010) 51.15.69.135:8080/wallet.html (Gonzalo)
(7010) 128.199.97.207:8080/wallet.html (Scott)
(7010) 51.15.69.135:8080/wallet.html (Gonzalo)
(7010) 128.199.97.207:8080/wallet.html (Scott)
01:32
Deleted Account
doing tmux for me made all the difference
G
01:33
Gonzalo
In reply to this message
Well, the fact is that tried restarting many times, this script was the only thing that made a difference, so...
01:33
Deleted Account
you don't exit remote correctly, and that causes lots of issues
Z
01:33
Deleted Account
i will next time
01:34
I exited everything, and closed my remote terminals, and seeing if it keeps going ok
01:34
seems like it's working fine
Z
01:34
Zack
I used to use screen for this. But once control D became possible, I didn't have to use screen any more.
MH
01:34
Mandel Hoff
I use control+D to exit Erlang prompt. Works good unless my finger slips and hits control+C and that's pretty bad.
Z
01:35
Zack
There is a button to undo control C
01:35
And return to the erlang prompt
01:35
Deleted Account
all about find what works, and I keep notes
G
01:35
Gonzalo
But I'm not exiting at all, I'm always in
01:36
01:36
Deleted Account
I move my laptop alot
01:36
and run the node int the cloud
MH
01:36
Mandel Hoff
You live in the matrix.
01:36
Deleted Account
and also miners right now
G
01:37
Deleted Account
cool.. making some money lol
01:38
i'm going to build a mining rig for this project, so doing that this weekend
01:38
first one.. so see how that goes haha
01:39
only small one like 2 gpu
Z
01:39
Zack
great
01:40
Deleted Account
looks like I'm the only one mining right now
01:40
I got the last 2 blocks
Z
01:40
Zack
I think the reason mine died is because I just shut my laptop without disconnecting from my vps or doing control+D to move the program to the background
01:41
Deleted Account
yep.. that's exactly what my problem was
G
01:42
Deleted Account
me too.. digital ocean node/mining pool and then 2 mining VPS servers going
G
01:42
This is my desktop right now :-(
Z
01:43
Zack
you have 4 monitors? haha
G
01:44
Gonzalo
yeah, and need more :-(
01:44
π
01:44
First time I see you smiling... Nice!! ππ
Z
01:46
Zack
I am at a hostal and don't have a desk. working from bed on my laptop now.
01:47
I am thinking I should update the syncing library so instead of downloading everything from 1 peer, you download different blocks from different peers
MH
01:51
My 1 monitor is enough for me. You must have more than 2 eyes.
G
01:52
Deleted Account
i did 2x 40β tvs before and was too much
Z
01:52
Deleted Account
felt like mission control nasa lol
G
01:52
Gonzalo
In reply to this message
haha I have lots of things to monitor at the same time, that's why... Would prefer to have just 1 monitor!
01:54
and Lambos, and girls, and... haha
Z
01:54
Zack
yes. I expect that we will all be able to afford many fine desks soon
01:55
Deleted Account
I work for another blockchain platform that just launch their token and took 3 months and so much effort to get listed
Z
01:55
Zack
on an exchange?
01:55
Deleted Account
yes
01:55
so many shitcoins
01:55
erc20
01:55
many many
Z
01:56
Zack
it is kind of nice not having an exchange. it is more like a market place where you can haggle to find the best price.
I sold my Augur Rep before they were on any exchange.
I sold my Augur Rep before they were on any exchange.
01:56
Deleted Account
worth it
Z
01:56
Zack
an exchange is less effort
G
01:59
Deleted Account
i donβt p2p trade
01:59
too many scammers βΉοΈ
Z
01:59
Zack
the exchanges can scam you too.
02:00
it would be really cool if we could set up atomic swaps to some other cryptocurrency.
Then you could p2p trade without risk of being scammed.
Then you could p2p trade without risk of being scammed.
02:00
the lightning transactions on amoveo are a type of atomic swap. So the code is already existing on Amoveo's side.
G
02:01
Gonzalo
In reply to this message
really! I hope in the next future the number of shitcoin will go down
02:01
Deleted Account
Go down? I'd prefer they disappear
G
02:04
Gonzalo
In reply to this message
Yes, there are only a few usefull coins/tokens that also not started from an ICO
02:04
Deleted Account
there's some really solid decentralized exchanges coming on the market. i'd look at something like ddex.io They're back by the Hydro Protocol team and look like they're in it for the longterm https://thehydrofoundation.com/
02:06
Deleted Account
I remember the old days of dash mining, you're better off buying the coin directly. My brother did that and has 10x the position I had. π. So for those who are thinking of mining for profit, think again. Remember to factor in your opportunity cost. So unless you don't have a cost and willing to help the network, then buying is the best option. Just my 2 cents.
Z
02:07
Zack
Amoveo allows for a better kind of decentralized exchange.
You use synthetic assets on Amoveo to get a good price to buy bitcoin or eth or whatever. Amoveo markets match trades in single price batches, so you can trade at the actual market price.
Then you use an atomic swap to switch synthetic Eth for regular Eth at a 1-to-1 ratio.
You use synthetic assets on Amoveo to get a good price to buy bitcoin or eth or whatever. Amoveo markets match trades in single price batches, so you can trade at the actual market price.
Then you use an atomic swap to switch synthetic Eth for regular Eth at a 1-to-1 ratio.
G
02:11
Gonzalo
Zack, right now what is the incentive to run a full amoveo node? With the GPU miner, solo mining from a full node will not be profitable anymore.
02:12
Deleted Account
at this point it's more about keeping the network alive, with node and miner...
Z
02:12
Zack
In reply to this message
even with a GPU miner, for now it is still more profitable to run your own node instead of using a mining pool.
Thinking more long-term, you can make a profit from running a node a couple different ways: by letting people make channels with you, and they can make lightning payments through you. By letting people make channels with you, and you run markets that they can trade in.
Thinking more long-term, you can make a profit from running a node a couple different ways: by letting people make channels with you, and they can make lightning payments through you. By letting people make channels with you, and you run markets that they can trade in.
02:12
Deleted Account
Doesnt the pool with most hashrate find the most blocks?
02:13
Deleted Account
the token won't have a value if the network dies
Z
02:13
Zack
so if you had a website where people could bet on sports using Amoveo for security, then your website would involve running an Amoveo full node.
G
02:15
It's a lot difficult for solo to find a block if the hashrate isn't a lot compare to pools
Z
02:16
Zack
if someone wrote a better pool, then mining with a pool will become more effective. Right now the pool isn't very good. you make more VEO mining on your own node.
Right now the pool only pays you if you find a block.
Right now the pool only pays you if you find a block.