Amoveo ♥🧿
1 March 2018
G
10:25
Gonzalo 
sync cron
sync cron
absorb block 9120
absorb block 9130
absorb block 9140
sync cron
syncing with this peer now [-7,[-7,34,229,146,193],8080]
trade peers
absorb block 9150
get their top header
talk_helper failed_connect 1
talk_helper failed_connect 1
get headers
server crashed.
header
removing peer [-7,[-7,34,229,146,193],8080]
command was header
removing peer [-7,[-7,34,229,146,193],8080]
sync cron
sync cron
sync cron
sync cron
absorb block 9160
absorb block 9170
absorb block 9180
sync cron
absorb block 9190
sync cron
sync cron
Z
10:25
Zack
oh he is resyncing.
G
10:25
Gonzalo
yeah
MH
10:26
Mandel Hoff
Yes, I'm starting from 0, at 2770 now and making progress
G
10:30
Gonzalo
Im stuck again: 
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron

(amoveo_core_prod@amoveo-scaleway-03)24> block:height().
9190
(amoveo_core_prod@amoveo-scaleway-03)25> sync cron
Z
10:31
Zack
your website says you have 9197
10:31
which is how many I have. so we are synced together.
10:31
and now Mandel is synced too
G
10:32
Gonzalo
yes, it has updated a few blocks without any warning:
Z
10:32
Zack
so lets try mining a block to see if it propagates.
We need to be in sync_mode:normal().
G
10:32
Gonzalo 
sync cron
sync cron

(amoveo_core_prod@amoveo-scaleway-03)24> block:height().
9190
(amoveo_core_prod@amoveo-scaleway-03)25> sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron
sync cron

(amoveo_core_prod@amoveo-scaleway-03)25> block:height().sync cron

9197
(amoveo_core_prod@amoveo-scaleway-03)26> sync cron
sync cron
10:32
In reply to this message
👍
MH
10:33
Mandel Hoff
I'm at 9197. Turning on miners in a few seconds...
G
10:35
Gonzalo
mining right now
MH
10:35
Mandel Hoff
9199
G
10:35
Gonzalo
still 9197
Z
10:35
Zack
looks like the block was correctly forwarded to my node
10:36
I noticed Gonzalo wasn't on our lists of peers, so I added him manually and tried to add him to both of your lists too.
10:36
but I think I didn't do it quick enough
G
10:36
Gonzalo
still 9197
10:37
want me to try anything?
MH
10:39
Mandel Hoff
9200
G
10:39
Gonzalo
9197
Z
10:40
Zack
it worked this time. the new header got pushed to Gonzalo
MH
10:40
Mandel Hoff
9202
G
10:41
Gonzalo
block height 9197 / api height 9203
Z
10:41
Zack
even though he is receiving headers, Gonzalo's node is failing to automatically download blocks from us.
I think it is because a bunch of peers got added to our list just now
MH
10:42
Mandel Hoff
Should I add him manually?
G
10:42
Gonzalo
block height 9197 / api height 9204
Z
10:42
Zack
Gonzalo did you do sync_mode:normal(). ?
G
10:42
Gonzalo
In reply to this message
yes, before starting the c-miner
Z
10:44
Zack
ill try forcing the blocks to Gonzalo to see how broken it is
MH
10:44
Mandel Hoff
I have about 15 minutes before I have to quit for the night. Please let me know if there's anything I should try or setup for the overnight hours. I'll be happy to setup my node however works best for testing whatever you would like to test.
10:45
Deleted Account
i have to delete my database and start from scratch
10:46
i was trying to mine and get blocks, but no one talks to me
Z
10:46
Zack
It is hard to guess what is most useful to test.
It was a lot of help today
10:46
it seems like Gonzalo is staying in sync properly now.
G
10:46
Gonzalo 
syncing with this peer now [-7,[-7,52,234,133,196],8080]
trade peers
get their top header
already synced with this peer
syncing with this peer now [-7,[-7,52,234,133,196],8080]
trade peers
sync cron
sync cron
get their top header
already synced with this peer
sync cron

(amoveo_core_prod@amoveo-scaleway-03)59> mining data block hash is "D5xzkbGug9sAS/0sIC4BR3BYjM9w7bMn3SaoRoZqWhw="
(amoveo_core_prod@amoveo-scaleway-03)59> api:height().sync cron

9208
(amoveo_core_prod@amoveo-scaleway-03)60> sync cron
(amoveo_core_prod@amoveo-scaleway-03)60> block:height().
9208
(amoveo_core_prod@amoveo-scaleway-03)61> sync cron
sync cron
sync cron
10:46
Done!
Z
10:47
Zack
my node deleted everyone else from the peers list, so it wont sync.
G
10:47
Gonzalo
In reply to this message
The same goes for me, its almost 4AM here...
Z
10:47
Zack
This is probably what happened that was stopping your guys from syncing before.
MH
10:47
Mandel Hoff
Nice. I'll mine hard for a while longer. See if you stay sync'd with me.
Z
10:48
Zack
I guess we should leave the new code up for now. I will play with it a little more, and maybe we can use it for mainnet launch
Deleted joined group by link from Group
G
10:49
Gonzalo
In reply to this message
nice 👍. I'll let the node on + miner working. Will report in about 4 hours time
MH
10:50
Mandel Hoff
Ok, I'll do another ~7min of hard mining. If you stay sync'd then I'll leave it up overnight - right?
Z
10:50
Zack
sounds good.
MH
10:50
Mandel Hoff
👍
Z
10:50
Zack
I just re-added you guys to my list of peers. so I think it will stay synced
10:50
I was receiving headers correctly, but without you in my list of peers I wasn't downloading the blocks
MH
10:52
Mandel Hoff
There are about 9 active (not me) miners on my pool, so they'll probably continue through the night mining - just not at the burst speed I'm doing now.
Z
10:52
Zack
sounds good.
10:52
Deleted Account
ok my node is back up
Z
10:52
Zack
all 3 seem to be staying in sync now
10:52
Deleted Account
starting miners
Z
10:53
Zack
so I guess I just need to fix the problem where peers are disappearing from the list
MH
10:53
Mandel Hoff
I may speed test tomorrow with miners for 10-20 minutes. Probably will test about 10x my speed now, but probably won't run that fast on main net.
Z
10:54
Zack
cool
10:54
Deleted Account
i just sync'ed and already 4 blocks behind
G
10:55
Gonzalo
starting and syncing node 51.15.212.91 as well
MH
10:55
Mandel Hoff
I'm excited for when the sync is working great and we move on to channels, governance, and derivatives. That was very exciting stuff, but I haven't worked on that at all in weeks.
Z
10:56
Zack
yes
10:56
In reply to this message
I see this node appeared in the list of peers
MH
10:57
Mandel Hoff
I could probably build a betting site, but honestly - I don't have the courage to run it. Legal concerns petrify me.
Z
10:57
Zack
In reply to this message
Scott, did you see that we switched branches
10:57
In reply to this message
yeah, it is true.
I am setting up a permanent residency in a different country for this reason.
MH
10:57
Mandel Hoff
I can stop mining if that helps Scott sync. Let me know.
Z
10:58
Zack
how about a lightning payment node
10:58
I think that scott is using the master branch code, so he wont be able to sync.
10:58
Deleted Account
yes.. i'm on the master
10:59
i can switch to the header branch easy
Z
10:59
Zack
I think it is more stable with 4 nodes than 2.
If one of them drops peers, then the other 3 remind it.
10:59
Deleted Account
everyone on that new branch then?
Z
10:59
Zack
it seems like we are switching branches, at least until Mandel is done sleeping
10:59
Deleted Account
ok
F
11:01
Francesco @ Simply
In reply to this message
What are the profits in running a betting market server? Can you set it up to take commission on each bet?
Z
11:01
Zack
There are a couple massive bandwidth spikes because you guys just downloaded my blocks. but besides that the bandwidth is looking really small
11:01
In reply to this message
it is programmable. you can charge any sort of fee you want.
The one I programmed has a flat fee per trade that you can set in the configuration file.
11:02
block propagation is working much better now.
G
11:03
Gonzalo
looks great
11:05
Nodes 163.172.144.202 and 51.15.212.91 synced and mining, both at height 9228
Z
11:05
Zack
great
G
11:05
Gonzalo
And node 51.15.69.135 syncing
MH
11:06
Mandel Hoff
I'm at 9229. I'll stay on a few more minutes. Very happy sync branch looks promising.
Z
11:07
Zack
yes, I am happy about this too.
G
11:07
Gonzalo
9231 here
11:07
mining goes fast
11:07
In reply to this message
👍
MH
11:07
Mandel Hoff
Yes, betting and derivatives is 1000x better than my pool for a business that can execute.
11:07
9231 on my pool
11:08
9232
11:08
I spin up extra miners when testing sync so we dont have to wait as much between block tests.
Z
11:09
Zack
yes, you are a lot of help Mandel
G
11:09
Gonzalo
9232 an all my 3 nodes!
Z
11:09
Zack
I don't know about 1000x
mining pools make a lot of money
G
11:14
Gonzalo
wow, this is syncing like a swiss watch
Z
11:14
Zack
great :)
G
11:15
Gonzalo
all 3 nodes got block 9240 at the same time
11:15
👍👍
Z
11:15
Zack
awesome
11:15
that means it should be possible to run more than one mining pool at a time now.
So Scott wont be eternally on his own fork.
G
11:15
Gonzalo
yeah, good job!
MH
11:16
Mandel Hoff
9241, spinning down miners now.
Z
11:16
Zack
ok, sounds good
MH
11:17
Mandel Hoff
Normal (not me) pool miners will continue overnight. Fixes look great. Very exciting.
11:30
Deleted Account
ok on the push_headers
11:30
getting database.. i did prod-clean prod-blocks.. is that good enough?
11:31
it's doing sync cron lots
Z
11:32
Zack
yes, sounds good
11:43
Deleted Account
9247
11:43
and mining
11:44
I'll let it go through the night
Z
11:45
Zack
In reply to this message
great. thanks for testing
12:07
Deleted Account
my node is falling behind
Z
12:10
Zack
And you are the only one mining. I guess it is not recovering from forks correctly. Thank you for finding this out.
12:19
I think Gonzalo said he is mining too.
So I am not sure why your node is falling behind.
I see that you are still in the list of peers.
12:22
I see that my node is just trying to sync with the same peer over and over, ignoring all the rest. it also is falling behind.
12:25
It eventually escaped the loop. and now we are both synced
12:26
I think this is because I am using a bad random number generator to decide which peer to sync with next. It is depreciated, so I will upgrade.
12:35
oh, I think my node actually fell behind because I switch back to the old version of the code accidentally
12:51
Deleted Account
I mined 9260, and mandel's pool didn't get a block for 2-3 min, but it never accepted my block.. mined it's own block, nullified my block again..
Z
12:51
Zack
If there are 10 of us, but only one has the block, and we all start asking randomly, there about a 1/8 chance that none of us know about the block, even after we have asked 3 random peers.
It would be better if we asked the person who gave us the headers first, since they are more likely to have the block.
12:52
even worse, sometimes when we try to contact a peer we get stuck in a loop, and it take a whole minute to finish and move on to the next peer.
12:56
Deleted Account
I'm mining with about 12 M/h right now.. 3 miners 25 cores
Z
12:56
Zack
Still, it seems more reliable than the old version
12:56
Deleted Account
i'm getting sync'ed... but doesn't help if i mine a block and mandel's pool doesn't accept it
Z
12:57
Zack
he will accept it if you mine on the top.
12:58
are you sure you switched branches? your node is acting like mine did when I was on the master branch.
12:58
we all switched to push_hash branch
12:58
Deleted Account
let me check
Z
12:59
Zack
git branch should tell you which branch you are on
13:01
Deleted Account
push_headers
13:03
i pulled your last changes for push_headers
13:04
restarting machine
13:06
9275
Z
13:07
Zack
I'm going to sleep
K
13:07
Kenny
thats where im at too :(
13:07
Deleted Account
restarting miners then me too
K
13:07
Kenny
have a good night
Deleted joined group by link from Group
Deleted joined group by link from Group
Deleted joined group by link from Group
16:06
Deleted Account
my full node seems to be stuck any pointers?
16:07
mining data block hash is "nlaSOL16Faqev9aYkP8ZVQLkDRTPjPH61VGCtz/2k9E="
many headers [-6,5001,0]
many headers [-6,5001,5000]
many headers [-6,5001,8781]
(amoveo_core_prod@localhost)15> api:height().
8781
16:11
also (amoveo_core_prod@localhost)19> block:height().
0
L
18:03
Laur
why though, throw will exit and return that string, so the script won't return false, as the next line suggests
18:08
last thing I wrote was on issue 4., which is legitimate
18:09
anyway, regarding the more important erlang part of the code, I think I can only use XREF and Dialyzer, have you used any of these already?
Z
18:09
Zack
Sorry, I was starting to think you were a bot posting advertisements for that tool
L
18:10
Laur
no lol, this was 4 btw:
18:10
4
Z
18:13
Zack
yes it is clearer if we comment out "return false" since it wont execute.
18:13
In reply to this message
no.
L
18:14
Laur
ok, I'll run them and see how they go
Z
18:21
Zack
24 hours until main net launch.
MF
18:23
Mr Fox
Sticker
Not included, change data exporting settings to download.
😂, 12.2 KB
John Tromp joined group by link from Group
MF
18:24
Mr Fox
18:24
if it dies, will we lost our’s coins ?
18:33
Deleted Account
why so pesimistic? the only big issue is get coins lost. if coins can be guaranteed even nodes crases or syncing has issues, i dont think amoveo will dessappear. I guess losing some time mining and dont get reward bc there are sync problems or nodes crashes is afforable. the big problem is if we have already minned and found blocks and for technical reasons (net down, updates...) this blocks could be lost. the last scenario could happen?
thomas s joined group by link from Group
Z
18:34
Zack
In reply to this message
Yes.
18:35
In reply to this message
There are disaster scenarios that are un-recoverable.
Like hyperinflation, or excessive forking.
18:36
In reply to this message
But usually you are correct.
The vast majority of errors will just make the network go down for a few hours, and we can fix it.
NH
19:11
Nick Harris
Has anyone tested if there are diminishing returns for mining via parallelisation?
19:12
Like would it be better to have several instances mining vs one bigger one with more cores/threads
Deleted joined group by link from Group
Z
19:29
Zack
In reply to this message
I haven't done this test.
The miner comes with a speed measuring tool. So it wouldn't be hard to find out.
19:36
For the last 5 hours or so we have been using the push_headers branch for the testnet, and it has been going well.
In preparation for the mainnet launch, I will now do a hard-fork to the code in the master branch.
We will launch a new testnet for the rest of the day. This testnet will have almost identical code as the mainnet launch tomorrow will have.
AB
19:43
Asda Bayor
do you know how many miners there are at any time on the testnet?
Z
19:43
Zack
In reply to this message
no.
19:56
Deleted Account
After long time of "did not find a block..." i have found a work 30 min ago:
40578656100332569062995786206577402548872941108678547353985212030925471679153
Found a block. 2
but i cant see in my pubkey any change, (i am looking in my wallet and in your wallet) Am i doing smth wrong? my keypub BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=
Z
19:59
Zack
this is my fault. I restarted the node and I forgot to change sync_mode to normal.
19:59
pretty soon there will be a hard fork, and then difficulty will be low so it will be easy to test out mining.
20:01
Deleted Account
do you mean i have lost the block because your sync is not in normal mode, is it? but i was mining through my full node and it was in sync mode normal. it doesnt matter?
Z
20:02
Zack
In reply to this message
oh, I thought that you were connected to my mining pool.
If you are mining with your own full node, then what is your ip address? what is the block height?
20:03
Deleted Account
http://209.250.248.93:8080/wallet.html "height ",9354]
Z
20:04
Zack
In reply to this message
are you BPFU.... ? because it looks like BPFU mined the top block
20:05
oh, yes you are BPFU, you already said.
20:05
api:balance().
20:10
it looks like you correctly shared the block you mined to the network.
20:10
Deleted Account
yes, i now i see in both the web and with the command. How long it takes to appear the balance changes?
Z
20:11
Zack
I think you copy/pasted your address wrong before. This is your address:
BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=
20:11
it should appear instantly in the website you host.
Sharing to the other nodes should happen within 30 seconds.
20:15
Deleted Account
It is the once i pasted. I will wait untill next block and see if i have any problem in getting the balance updated. thanks Zack
Z
20:16
Zack
oh, you are right. the address was correct.
lw
20:20
lijun wang
when mainnet go online?
Z
20:21
Zack
22 hours 39 minutes.
M
20:22
Minieep21
Has anyone released a Windows GPU miner?
Z
20:23
Zack
In reply to this message
there is no GPU miner yet.
WL
20:28
Wilson Lau
I can't sync the blockchain
20:28
Z
20:29
Zack
In reply to this message
we just did a hard fork. Delete all the blocks and update the code.
20:29
we are on block 0.
WL
20:29
Wilson Lau
I see
Z
20:35
Zack
the difficulty on the new blockchain is 1/2 what it was on the blockchain yesterday.
20:36
Deleted Account
Just buy a ryzen7 1700x computer for mining Amoveo
20:36
bought
Z
20:41
Zack
In reply to this message
cool. It looks like this CPU will work well until GPU mining becomes possible.
20:47
In reply to this message
将有可能在22小时内开采主链
21:11
Deleted Account
we are master branch now?
Z
21:12
Zack
In reply to this message
Yes. Máster branch. Restarting from block 0.
21:14
Deleted Account
ok showing block height 0
21:15
said nothing to sync
21:16
prod-clean prod-block?
Z
21:16
Zack
Yes. That is correct. We are on block 0
21:19
Deleted Account
If this error happens while connected to the public mining node, then it can probably be safely ignored.
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
21:23
so i turned on the miner, showing above error due to 0 i guess
21:24
found a block
21:30
Deleted Account
I am getting a continuous sync cron message after doing prod clean and restart
21:30
Is this normal?
21:31
Deleted Account
sync:start().
21:31
3 blocks
21:32
and my keys didn't change right?
21:32
Deleted Account
When I do prod attach I am interrupted by the same sync cron message when I try to type the command.
21:32
Deleted Account
node key is the same.. and my main address and key should stay the same I pretty sure
21:33
make prod-restart
21:33
sync:start().
21:33
master branch, git pull before restart
21:34
Deleted Account
Done that
21:34
I'll retry
21:34
Deleted Account
in quick mode,, have to sync_mode:normal().
21:34
ok so I have 3 miners going and finding blocks
Z
21:34
Zack
In reply to this message
Good.
21:35
In reply to this message
Yes
21:35
Deleted Account
Ok so it will find a block eventually?
Z
21:36
Zack
In reply to this message
you can check. api:pubkey().
21:36
Deleted Account
BTW I got the node running in pi🙂
Z
21:36
Zack
In reply to this message
correct. you figured it out. How did you do that?
was it sync.md?
21:36
Deleted Account
yep..node key is the same.... and wallet key I assume won't change at a hard fork, but wanted to make sure
Z
21:37
Zack
In reply to this message
That is great. please write down the steps for the community
21:37
Deleted Account
i think so..
21:37
Deleted Account
In reply to this message
Sure l will post on reddit
21:38
Deleted Account
it would be better to do a pull request on the github..
21:40
i have quit a few blocks now
21:42
and the miningpool fee is 20% now
21:42
?
21:44
doesn't look like you are getting my block Zack
Z
21:45
Zack
yes, looks like it
21:45
Deleted Account
i checked your explorer..5 blocks
21:45
no headers
21:45
on mine either
21:46
block:height().
5
(amoveo_core_prod@anode)12> sync cron
sync cron
api:height().
5
21:46
just light wallet doesn't show headers yet i guess
G
21:47
Gonzalo
I reinstaled master branch on my nodes, Im not getting any block
21:48
peers:all shows Mandels, Zacks and my two 51.15 nodes
21:48
Deleted Account
many headers [-6,5001,0] <-- get headers on wallet. but api and block height says 5 in terminal
21:48
i mined 5
R(
21:51
Rlyyy (Mr Green)
amoveopool.com down?
21:53
Deleted Account
Looks like it has been for a few hours
MH
21:53
Mandel Hoff
Yes, upgrading to new main net. All balances will need to be reset.
Z
21:54
Zack
In reply to this message
yes, the light node console has lots of errors. thanks for pointing this out.
22:01
ok, looks like we are all at height 5
22:03
element(16, block:top()). tells how many VEO exist.
MH
22:03
Mandel Hoff
Ok, I'm updated to node 5. Still fixing up the amoveopool.com
Z
22:05
Zack
A bunch of old peers got added to our list.
lets see how well they clean out when we find the next block.
22:05
make sure you are in sync_mode:normal().
otherwise you wont get any blocks.
22:06
Today is a sort of practice launch for tomorrow
22:06
dress rehersal
R(
22:06
Rlyyy (Mr Green)
In reply to this message
How do I set up the C miner with your pool in miner.erl?

Is this correct?
-define(Peer, "http://amoveopool.com/work").%for a mining pool on the server.
Z
22:06
Zack
In reply to this message
I think you have to use the miner that Mandel made if you want to connect to his pool
22:06
Deleted Account
Speed test function was disabled?
Z
22:07
Zack
In reply to this message
no
MH
22:07
Mandel Hoff
You'll need to use my miner here:
https://github.com/Mandelhoff/AmoveoMinerCpu
Works for Ubuntu or Windows.
R(
22:07
Rlyyy (Mr Green)
too bad, I am on macos
Z
22:07
Zack
my pool works with macos
R(
22:08
Rlyyy (Mr Green)
In reply to this message
so for C miner I have to use yours?
Z
22:08
Zack
yes
22:08
Deleted Account
I have a suggestion : Ask the user for the port location during the node setup.
Z
22:08
Zack
but my pool is open source. so you can use c-miner with many pools
22:08
Deleted Account
MH
22:10
Mandel Hoff
My mining tool might compile for macos. The RestCPP and other dependency install would probably be the only tricky part. The rest is just c++ and gcc.
22:10
Deleted Account
Undefined function miner:speed_test/0
22:10
Deleted Account
block:height().
7
(amoveo_core_prod@anode)15> sync cron
api:height().
7
R(
22:10
Rlyyy (Mr Green)
do I build the miner on mac with same command as for ubuntu? sh build_ubuntu.sh
Z
22:11
Zack
In reply to this message 
bash-3.2$ cd ../amoveo-c-miner
cd ../amoveo-c-miner
bash-3.2$ sh build_ubuntu.sh 
sh build_ubuntu.sh
miner.erl:105: Warning: variable 'E' is unused
miner.erl:116: Warning: no clause will ever match
Eshell V8.3  (abort with ^G)
1> miner:speed_test().
miner:speed_test().
ok
2> halt().
halt().
bash-3.2$ ./amoveo_c_miner 
./amoveo_c_miner
speed test starting
speed result: 0.181465 megahashes per second per CPU
bash-3.2$ git pull
git pull
Already up-to-date.
22:11
In reply to this message
great
22:12
In reply to this message
yes.
22:12
Deleted Account
In reply to this message
I am still at 5
22:14
Deleted Account
can't check wallet balance on light wallet.. no headers and nothing shows
Z
22:16
Zack
In reply to this message
I updated the name of the file because you asked this useful question. thank you.
22:16
In reply to this message
did you sync_mode:normal(). ?
22:16
Deleted Account
Yep
Z
22:16
Zack
what is your explorer url?
22:17
my_ip:get().
MH
22:20
Mandel Hoff
I'm still at 5. sync normal.
22:21
Deleted Account
{124,40,244,94}
Z
22:27
Zack
I found something that was stopping us from syncing if we talked to an old peer first.
22:28
Deleted Account
ok i can update in 30 min
Z
22:29
Zack
I pushed a fix
22:29
Deleted Account
ok.. let me update fast
22:31
ok updated and back online
MH
22:32
Mandel Hoff
I'm updated. height 10 now.
22:32
Deleted Account
same
Z
22:32
Zack
only scott is on 11
22:32
Deleted Account
11
Z
22:33
Zack
In reply to this message
did you sync_mode:normal(). ?
R(
22:34
Rlyyy (Mr Green)
If I create a wallet on http://159.89.106.253:8080/wallet.html right now, can I use that wallet for mining tomorrow?

Or do I have to create a new one when mainnet launches?
Z
22:37
Zack
In reply to this message
you can use that one.
R(
22:38
Rlyyy (Mr Green)
last question then: is it normal that the c miner says "did not find a block in that period" at the moment?
Z
22:38
Zack
yes, that is normal.
R(
22:38
Rlyyy (Mr Green)
thx guys, appreciate the help 🙂
Z
22:42
Zack
my node gets stuck in a loop where it only tries to contact one peer.
22:45
Deleted Account
In reply to this message
yes
Z
22:47
Zack
ok, we are all on 11 now
g61906 joined group by link from Group
22:57
Deleted Account
ok who else is mining?
22:57
Deleted Account
@Mandelhoff on line 456 of AmoveoMinerCpu.cpp I see an "L" outside of the quotes that whichs fails compilation on my Ubuntu side anyway. Removing seems to work.
22:59
Deleted Account
me too
22:59
mining
Z
22:59
Zack
I pushed a fix for the random number generator. Now we don't keep talking to one peer forever.
23:01
Deleted Account
updated
MH
23:01
Mandel Hoff
In reply to this message
L"[\"mining_data\"]"
The L makes a wide-char literal. I'm pretty sure that's supposed to be there. Not sure why it causes an error on your system.
23:02
Glad you worked around it.
23:03
Deleted Account
In reply to this message
Where there is a will there's a way.
23:03
Deleted Account
so far i've mined all the blocks..
23:03
12
23:03
Deleted Account
i dindt find anyone yet
G
23:04
Gonzalo
I'm at 13
23:04
so you find a new one
23:04
Deleted Account
ok great
23:04
let's see if i get it
G
23:04
Gonzalo
Im mining but found none
23:05
Deleted Account
i'm at 13
23:05
says i mined 1-12
Z
23:05
Zack
cool
23:06
Deleted Account
not sure who mined 13
Z
23:06
Zack
someone is using my mining pool
23:07
Deleted Account
I can't handle this
["mining_data"]
Z
23:07
Zack
now we are all on 13
G
23:07
Gonzalo
👍
23:07
Deleted Account
i am at 11
Z
23:08
Zack
In reply to this message
sounds like you are using the wrong port.
the default 2 ports are 8080, and 8081
23:09
Deleted Account
this message is from the node which is by default running on 8080
Z
23:09
Zack
In reply to this message
your port isn't externally available. we can't send you headers.
23:09
Deleted Account
oh
23:09
but how did i get to 11?
Z
23:10
Zack
when you first turned on, it pulled blocks to sync up. then we mined 2 more, so you fell behind
23:10
Deleted Account
i synced up at 10
23:10
wait no
23:11
i need to do some port forwarding i guess
Z
23:11
Zack
you downloaded 11 headers at that point, so your node kept trying to get the next block for it's extra header? maybe?
23:11
or you can join a mining pool
23:11
Deleted Account
what's the fix the light wallet not showing headers, and can't get account balance?
Z
23:11
Zack
I think I changed the header format slightly
23:12
I also changed the initial difficulty, but I already fixed that.
23:15
14 spread around pretty quick
N invited Valentine Z
23:15
Deleted Account
the miner wont stop if i ctrl-c right?
Z
23:15
Zack
it will stop
23:15
Deleted Account
open-cl miner
23:15
is there a way to exit?
Z
23:15
Zack
I guess you can put it inside of screen if you want it to run in the background.
23:16
sh clean.sh
23:16
Deleted Account
i use tmux. works great
23:16
Deleted Account
Yeah same
Z
23:16
Zack
yes, I read good things about tmux
23:16
Deleted Account
ah yes tmux
M
23:20
Mike
what is current way of restarting and syncing? looks like many updates last day, and old way doesn't work for me anymore
23:20
after git pull last version and make prod-restart all it writes is 'sync cron'
23:21
and sync:start(). doesn't help either
23:21
there are only 15 blocks right now
M
23:21
Mike
oh, full reset?
23:21
ok, will see what I can do
Z
23:21
Zack
This is a practice launch for tomorrow. to make sure it goes well.
M
23:22
Mike
third sync:start(). did the trick
Z
23:22
Zack
great
MH
23:22
Mandel Hoff
I think amoveopool.com is up and running now. I will monitor payouts, but looks good so far.
Z
23:23
Zack
In reply to this message
looks good.
23:25
Deleted Account
In reply to this message
If I were to just leave my things running on amoveopool with the new keys I got today will things just slide into the mainnet on launch or will I have to do something?
MH
23:30
Mandel Hoff
Right - anyone mining in to amoveopool.com should have to do nothing in the main net transition. The miner will sit in a "get work failed" loop until the pool comes online for main net. Addresses don't need to be changed either.
23:30
Deleted Account
Cool thanks @Mandelhoff
23:31
Deleted Account
mandels pool showed 18 as mine and then overwritten with his when he wrote 19
23:32
18 and 19 are his now. just like every time
Z
23:32
Zack
In reply to this message
Hopefully your blocks are becoming uncles less frequently now?
23:34
Deleted Account
i have 3 miners going just to have a fighting chance
23:34
we’ll see if i get any credit for blocks in the next couple hours.
MH
23:44
Mandel Hoff
Oh crap - Zack changed the epoc timstamp.
Z
23:47
Zack
I fixed the light node.
23:48
Deleted Account
23:48
Thomas @Mandelhoff try to compile miner on Ubuntu . Same error Thomas met?
MH
23:48
Mandel Hoff
Old epoc was this: 1482574978. New epoc: 15192951759
23:49
Deleted Account
In reply to this message
Yeah I just removed the L from line 456
23:50
Works fine as I have mined 1.04 on his pool already
23:50
Since it's been up with the new testnet
MH
23:54
Mandel Hoff
Payouts look good so far. It's doing create_tx for all the new accounts. Scott appears to be getting some blocks too.
Z
23:55
Zack
In reply to this message
great. thanks for checking this out
MH
23:55
Mandel Hoff
I updated my epoc, so confirmed blocks should show up on the next batch. I "confirmed" with he wrong timestamp on the first 25 blocks.
Z
23:56
Zack
The retargetting algorithm takes the median of 1000 blocks, so if 25 are off, that isn't a problem
23:56
Deleted Account
I deleted L. Works too.
23:57
Deleted Account
👍
2 March 2018
MH
00:02
Mandel Hoff
In reply to this message
The block chain is correct. Just my local dashbaord database has bad metadata cached.
Z
00:02
Zack
In reply to this message
Ok
00:05
Deleted Account
one hour without a block is normal?
Z
00:06
Zack
In reply to this message
It would take my computer about 3 hours to find a block. I have 0.36 mh/s. A block is 4 gigahashes.
00:07
Deleted Account
ok, i thought now with less difficulty would be more frecuent
Z
00:07
Zack
Yeah, I thought the difficulty was going to be lower too. I misremembered
00:08
It was good to test, because we will want to start the difficulty fairly high on main net.
MH
00:11
Mandel Hoff
👍
00:13
Deleted Account
00:13
i have already change the thread into 16. still just got this slow speed
00:14
Deleted Account
Pretty sure that's just one core
Z
00:14
Zack
In reply to this message
The speed test just measures 1 cpu.
This means you have about 8 mh/s. Very fast
00:14
Deleted Account
If you open htop you'll see 1 going bananas
Z
00:14
Zack
24 times faster than my computer
00:15
Deleted Account
Also you'll only see 1 thread from the parent process
00:15
Deleted Account
how could I know that really 16 threads working
00:15
Deleted Account
If you do that whilst mining you'll see 16
00:15
Load up the miner and like up htop
00:15
And you'll see all the processes
Z
00:15
Zack
In reply to this message
Thanks for the support Thomas.
00:15
Deleted Account
In reply to this message
Aye aye cap'n
00:17
Deleted Account
is that means i got 16 threads?
00:17
Z
00:18
Zack
In reply to this message
There is a value in miner.erl that needs to be changed from 2 to 16
00:18
Deleted Account
i already changed that
00:18
Deleted Account
In reply to this message
Load up another session or start a tmux session up and start the miner
00:19
The run htop and you'll see it running under the main process
00:19
You may need to install it via sudo apt install htop
00:20
Easiest way
Z
00:20
Zack
I use top
It works fine.
00:24
Deleted Account
yes it use 16cores
00:24
00:25
is that opencl miner the fastest right now?
00:35
Deleted Account
I have a private password that is wha i use when i unlock the node keys:unlock("Pass"), but i guess this Pass is not the private key, how i get the private key for my pub key?
Z
00:36
Zack
In reply to this message
Great
00:36
In reply to this message
Yes, but it is very hard to install.
00:37
In reply to this message
The encrypted private key is in _build/prod/rel/amoveo-core/keys/keys.db
00:38
Deleted Account
ok, so i have to save with this db with my life... thanks
00:40
Deleted Account
In reply to this message
cool
Z
00:41
Zack
In reply to this message
You might want to generate and store this file in cold storage. For ultimate security
00:42
Deleted Account
i guess in mainnet i can get the same keys as today, is ok?
Z
00:42
Zack
In reply to this message
Yes. The same key as now will work.
00:44
Deleted Account
the amoveo of each block is 1 after launch?
Z
00:44
Zack
Yes. But the community can change it
00:47
Deleted Account
I assume that 25 or 50 should be fine. Since if it set to 1 that the community can only increase the rewards of each block. That will make early bird like us hurt. The earlier miner should get more rewards
Z
00:55
Zack
In reply to this message
no, they can decrease it.
1 VEO is divisible into 100000000 Satoshis.
00:56
So there could be a block reward of 0.04 VEO, for example
01:00
someone mined 30 blocks, and they aren't sharing.
01:01
Deleted Account
api:height().
121
(amoveo_core_prod@anode)6> sync cron
sync cron
block:height().
77
Z
01:01
Zack
they only give us the headers, and don't let us download blocks
01:01
who is doing this?
I guess someone is running a solo-miner and their port isn't forwarded to the internet so we can't download their blocks.
01:02
Deleted Account
[1,2,3,4,5,6,7,8,9,10,11,12,13,24,25,28,49,50,51,52,53]
Z
01:02
Zack
so it isn't Scott. I can also tell by looking at your explorer.
01:03
they are sure mining fast
01:04
The bandwidth requirement will be a lot higher as long as this attack is sustained.
01:04
Deleted Account
i just updated to fix the headers, and no change to my miners
Z
01:06
Zack
The attacker has almost twice as much mining power as the rest of us put together
MH
01:06
Mandel Hoff
Thanks - I'll watch bandwidth, but so far not too bad.
01:06
Deleted Account
could not get block 310 from peer [-7,[-7,52,234,133,196],8080]syncing with this peer now [-7,[-7,209,250,248,93],8080]
Z
01:06
Zack
In reply to this message
yeah, we are all trying to download the blocks. Whoever mined them is not sharing.
01:07
It seems like the attack stopped.
01:09
Maybe it is a mistake that I never let the nodes push blocks to each other. This makes solo-mining not work, and in the worst case it makes solo-mining into an attack.
01:11
It looks like the network is recovering from the attack correctly. We should be back to normal behavior in about 2 hours.
01:12
Deleted Account
86 and 87 i just mined showed in the pool 😃
01:13
yes i agree the network is working much better today
01:14
no balance showing in light wallet yet
Z
01:14
Zack
In reply to this message
great, glad to hear it.
01:14
In reply to this message
once we get past height 132 then the light wallet should work again. For now the headers are wrong.
01:15
Deleted Account
i have installed a mining pool and when i configure the miner to locally mining to the mining pool, is ok, but when i try to configure other PC miner to the mining pool it shows the message "If you are running a solo-mining node..." once and again and does not shows anything like "did not find a block in that period", is ok? how i could know if the miner is well connected to the mining pool? (both miner mining to the same keyppub)
01:15
Deleted Account
ok.. i see that they are very high, but blocks are propagating correctly from what i can see.. at least between me and the pool
01:16
Deleted Account
PS: 2 hours and a half and no blocks, is this normal? 0,6mhs aprox
01:16
Deleted Account
.6 is probably per CPU.. are you using all your cpu's?
01:17
Deleted Account
yes, small cpu
Z
01:18
Zack
In reply to this message
are they in the same local network? probably you are putting the wrong url into miner.erl
in a local network the ip often looks like 192.168.0.x
01:18
Deleted Account
from what i've seen if you see "did not find a block in that period"
01:18
then that tells me my miner is working correctly
Z
01:19
Zack
In reply to this message
yes
MH
01:26
Mandel Hoff
01:26
We're cooking now!
Z
01:27
Zack
In reply to this message
wow! that is so much hash power.
3000 times faster than my computer
01:27
that doesn't seem possible
01:28
do you think someone is using a gpu
01:28
?
OK
01:28
O K
I've been wondering if someone was working on their own GPU miner to keep to themselves
01:28
Deleted Account
i contribute 8m with my cpu
MH
01:30
Mandel Hoff
I still think there i something wonky about the estimated hash rate based on difficulty. I think it's "fair" to all my pool's miners, hence not critical - but, I think somehow the difficulty target does not actually match the # of hashes to hit that target. Probalby not gpu. I spun up my farm and was doing about half of that work.
01:30
Deleted Account
i only have 25 cores going for i think 12-13 m/h
01:30
cpu mining isn't much
Z
01:31
Zack
In reply to this message
maybe if a block randomly is found faster than usual, it estimates that as higher difficulty?
Better to add up the previous 10 block times and divide by 10.
MH
01:33
Mandel Hoff
No, it's the same thing we saw a few days ago when Diff was ~164Billion and blocks were being found on single cpu miners when it should take them 24 hours to do that.
01:33
Deleted Account
great. i was able to keep 109,
MH
01:34
Mandel Hoff
I didn't find the root of that, but the math really feels not quite right on difficulty -> nonces required to find a solution
Z
01:35
Zack
well, every period of 2000 blocks has the same difficulty the whole time
MH
01:35
Mandel Hoff
Again, whatever the cause, it's "fair". It just makes any hash rate estimates based on difficulty-per-time not very accurate.
s
01:35
scott_l | DeFi Pulse
is the main net still launching tomorrow?
01:35
Deleted Account
ok so the problems I was having the last 4 days are gone now..
Z
01:35
Zack
oh, is it because one bit is always a 1.
01:36
Deleted Account
the test is going to be.. i go to like 1/10 the hashing power do I still get to keep my blocks..
01:36
i will test this afternoon
Z
01:36
Zack
0105 for example is an invalid difficulty.
01FF -> 0180
01:36
the second byte always starts with a 1 bit
01:37
I think it doesn't matter
01:38
And this is only when we measure the amount of work. We can still store other difficulties in the header.
01:38
Deleted Account
BLlL <-- me.. so happy to be able to keep a block 🎉
MH
01:38
Mandel Hoff
Maybe - it probably is something like solution hash "scores" have some collision space. Yes, it's a "fair" problem so not critical to solve.
Z
01:39
Zack
In reply to this message
yes 8080.
01:40
In reply to this message
We can always do a hard fork if we figure out something is wrong.
01:40
In reply to this message
you can use the same wallet for main net tomorrow as testnet today.
01:41
In reply to this message
the miner wont change.
amoveo full node needs to be updated.
OK
01:41
O K
starting the node, make prod-go, should occupy that terminal right?
01:42
(it returns nothing and gives me the prompt immediately)
Z
01:42
Zack
In reply to this message
I start the node like this make prod-restart.
Have a look at this page for details https://github.com/zack-bitcoin/amoveo/blob/master/docs/getting-started/turn_it_on.md
MH
01:42
Mandel Hoff
In reply to this message
Yes, that sounds very reasonable.
01:43
Also, great job fixing the network sync problems. That was a very epic last minute solution.
Z
01:44
Zack
yes, i am glad we got this working in time for main net.
Probably it was a mistake on my part to undertake such a big change at the last minute.
MH
01:45
Mandel Hoff
That sync issue was pretty critical though, so great job.
OK
01:46
O K
it should not take long to sync one block right?
Z
01:47
Zack
In reply to this message
I think we sync about 25 blocks per second
MH
01:47
Mandel Hoff
We are at block 119 - should take under 2 minutes for sure.
OK
01:47
O K
Something is wrong
01:47
okay
01:49
Deleted Account
@Mandelhoff is smth weird in the mhs of the pool, for my keypub it appears 21 mhs and I am using to your pool with at most 2mhs
Z
01:51
Zack
In reply to this message
but it takes about 3-10 seconds to start downloading blocks after you tell it to.
01:52
In reply to this message
Well, lets see how it does at launch. Maybe it wont survive to the end of the day.
MH
01:52
Mandel Hoff
In reply to this message
Yes, the pool does a share-difficulty per timespan calc to estimate your rate. That estimation is somehow inaccurate. It's "fair" because all miners have the same boosted estimation.
OK
01:52
O K
How do you type when it's constantly polling?
01:53
'sync cron'
01:53
Deleted Account
ok thanks.
Z
01:53
Zack
In reply to this message
I guess I should turn off the 'sync cron' feature. it seems to be stable enough now that we don't all need to watch it all the time.
MH
01:54
Mandel Hoff
The mining tool hash rate is very accurate. That knows exactly how many nonces are attempted per time period, but the pool can not trust any miner to report it's hash rate. Aside note - the miner counts any "get work failed" time in the duration, which counts against hash rate.
Z
01:55
Zack
In reply to this message
I got rid of sync cron just now. so if you update the software, and restart it, then it should be fixed.
OK
01:56
O K
okay, thank you
MH
01:56
Mandel Hoff
01:56
Oooo... look at that sync go ! 👍
Z
01:56
Zack
To answer your question, I am able to type while messages are appearing because I use the shell from inside emacs.

You never have to leave emacs
01:57
Deleted Account
BC6 is tearing it up now
OK
01:57
O K
ha, emacs is cool but dvorak screws hotkeys up and makes it tougher to learn
Z
01:57
Zack
looks like we have overcome the attack without any problems.
01:58
Deleted Account
@Mandelhoff Last Shared says 11:21 PM, I am being using 2mhs for about 3 hours, this shares doesnt appears? i havent found any block, could be the reason?
Z
01:59
Zack
In reply to this message
oh, my mistake. Actually the attack started up a second time.
01:59
Deleted Account
sorry, for my key pub
Z
01:59
Zack
it is still happening
OK
01:59
O K
What is the proper way to update? I just git clone, make prod-build, make prod-restart and still "sync cron"
MH
02:00
Mandel Hoff
In reply to this message
what address?
02:00
Deleted Account
BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=
Z
02:01
Zack
In reply to this message
first turn it off. then update the code. then turn it on.
api:off().
halt().
git pull
make prod-restart
02:03
now we have finally overcome the attack.
OK
02:06
O K
before the git pull, at api:height(). = 142, sync:start(). started pulling them in about 10 at a time.
02:07
Now after the git pull, "trade peers, get their top header, get headers, don't have a parent for this header"
02:07
block:height(). 0
G
02:07
Gonzalo
My 3 nodes at 151, same height that in Mandels pool 👍
02:08
now 153, this goes fast
02:09
Mandel I like your pool's pubkey "BANkErs" 😁
02:11
oh, maybe is not yours, i dont see any payment from this pubkey
OK
02:12
O K
I started over 
git pull
Already up to date.
make prod-restart
don't have a parent for this header
don't have a parent for this header
don't have a parent for this header
api:height().
142
sync:start().
...
trade peers
get their top header
get headers
don't have a parent for this header
02:14 
block:height().
0
MH
02:14
Mandel Hoff
In reply to this message
Right - not mine. Big hasher though.
02:16
In reply to this message
I think what happened is your miner got a lucky share and my pool assigned you a difficulty that was unreasonably high. There is code to reduce share diff over time when no shares are received, but it may not be coming down fast enough.
02:17
I manually updated your share-diff value, so it's lowered now the initial share value.
02:18
Deleted Account
@Mandelhoff ok, my miners are correclty connected to your pool, is ok?
OK
02:19
O K 
api:off().
halt().
make prod-clean
make prod-restart

solved don't have a parent for this header issue
02:20
sweet looks like I'm 173/173
MH
02:22
Mandel Hoff
In reply to this message
Yes, I think your miner stats look ok. Just looks like you didn't find a share for a long time and perhaps the assigned difficulty was too high.
Z
02:22
Zack
In reply to this message
Great
02:23
Deleted Account
In reply to this message
but i dont see any change, the mhs still remains 21 and the time last sahred dont update until now (it changes untin 1pm)
MH
02:25
Mandel Hoff
In reply to this message
Is your miner finding shares? Your last "get work" request was ~5 minutes ago. The miner should be doing "getwork" requests several times per minute.
02:28
Deleted Account
In reply to this message
i have been 4 hours with 2mhs in cminer my node and 4 hours with 2mhs in Mandel pool. none found. the log with your minner are smalls: the last hour:Not valid share. Difficulty too low.Not valid share. Difficulty too low.

Not valid share. Difficulty too low.
Not valid share. Difficulty too low.
Not valid share. Difficulty too low.
### NEW WORK ###
Not valid share. Difficulty too low.
H/S: 1232117 S:0 S/Hr:0
H/S: 1232141 S:0 S/Hr:0
H/S: 1232179 S:0 S/Hr:0
H/S: 1232175 S:0 S/Hr:0
H/S: 1232185 S:0 S/Hr:0
FoundShare: bDiff:8332 sDiff:7510
02:30
In reply to this message
I dont know what could be
G
02:38
Gonzalo
Zack I found so far that the only wallet.html that is showing the height is yours at http://159.89.106.253:8080/wallet.html
02:38
Others are showing "0"
MH
02:40
Mandel Hoff
Not sure. Difficulty too low is an error when the miner submits a solution below their assigned share diff. I reduced your address's diff to 7000. I see the pool lowered it even farther and you have an updated "get work" request.
02:42
Hard to say if that bankers has gpu or not. 10 second blocks ~6/min Might just be a ton of cpu. Probably can't know.
OK
02:44
O K
I am able to get my node caught up, but it doesn't continue syncing after sync_mode:normal().
02:45
Deleted Account
hello i just checked my balance on amoveo pool and it is zero. did i miss something.?
02:46
Deleted Account
restarted node, update just now.. went from 3 miners 12 m/h to 1 miner 4 M/h
G
02:48
Gonzalo
First time I see this "invalid header" warnings```invalid header without enough worksync cron
invalid header without enough workmining data block hash is "CvviI0MIq96xz8C75jiRo96TWvEMvaksgnkPJDqElLU="
sync cron
sync cron
mining data block hash is "CvviI0MIq96xz8C75jiRo96TWvEMvaksgnkPJDqElLU="
invalid header without enough workinvalid header without enough worksync cron
sync cron
mining data block hash is "r6egeCM1KaLYY2ph9RLbfb+ilgx8ue2Vfg6bq8HDues="
sync cron
```
MH
02:49
Mandel Hoff
In reply to this message
Yes, Zack hard forked to block 0 to test for tomorrow's main net launch. Everyone followed to block 0 and all balances reset.
02:51
Deleted Account
so all the balance are lost ..? and mainnet will not have past blockchain.?
OK
02:53
O K
That's right @usmanspall
02:53
This is standard for testnets on any platform
02:54
Deleted Account
@potat_o thanks for informing me. Should delete all the keys. So tommorrow's mainnet will start from 0 again..?
I
02:54
Iridescence
That's what a testnet means - the coins do not carry over to the mainnet
OK
02:54
O K 
block:height().
186
sync:start().
nothing to sync

I have started over 3 times
02:55
You can reuse the keys if you like @usmanspall , yes it starts from zero
02:55
After sync_mode:normal(). my node just stops syncing, am I missing something?
02:58
Deleted Account
@potat_o alright thanks.
02:58
@potat_o as far as i remember you don't need to use sync_mode:normal
MH
02:58
Mandel Hoff
In reply to this message
Keys and addresses can probably stay the same. I don't think they stop working on main net launch.
02:59
Deleted Account
it will automatically change to normal mode after sometime.
02:59
Deleted Account
reset my node, and now mining 1/3 the hash rate.. i have 195 and the pool has 192
03:00
Deleted Account
@potat_o which miner are you using ..?
OK
03:00
O K
I'm not mining yet, still working on getting a stable node
03:01
I reset, let's see what happens when api:height is 196
03:01
Deleted Account
zach has 195 too
D
03:01
Denis
Seems like amoveopool.com down
G
03:02
Gonzalo
Mandel do you think your Ubuntu miner will work on Debian as well?
MH
03:02
Mandel Hoff
In reply to this message
👍🙈😱 Fixing... sorry, doing my best for a hobby project.
03:02
Deleted Account
Zack i was supposed to find a block 20 min ago: "found work
44233163302257823508909331938396468211391070930403223092693707058275957537785
Found a block. 2"
but i dont see any change in my balance (BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=) like last time, when you looked my balance you could see it and then my wallet see it. Could you try to see my balance again? if you want to see first my wallet: http://209.250.248.93:8080/wallet.html
OK
03:03
O K
Are the pools causing too much centralization for the network at this early stage?
D
03:04
Denis
In reply to this message
Thanks for your work. Your pool is the best way to start mining.
03:04
Deleted Account
In reply to this message
you might now be at the top height..
03:05
I went through 4 days of mining, and always getting overwritten, but today network is much much better.. make sure you are in sync
03:06
Deleted Account
In reply to this message
sorry, what you mean, there is somewere i can look for it?
03:08
Deleted Account
In reply to this message
you have to look at the pool or one of the other nodes light wallet and explorer
OK
03:09
O K
whose is that?
03:09
Deleted Account
this is mine but the other nodes have also
OK
03:10
O K
So are we stuck on this block because the pool went down?
MH
03:11
Mandel Hoff
Zack my mining pool is spamming errors like this causing my pool to not be able to have work available for miners:
litepro2@litepro2:~/amoveo-mining-pool$ sh attach.sh
Attaching to /tmp/erl_pipes/amoveo_mining_pool@litepro2/erlang.pipe.4 (^D to exit)
(amoveo_mining_pool@litepro2)1> first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
(amoveo_mining_pool@litepro2)1>
(amoveo_mining_pool@litepro2)1> first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 1-Mar-2018::19:09:08 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.20377.1> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.51750>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.20377.1>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},61169}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>},{<<"expect">>,<<"100-continue">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 1-Mar-2018::19:09:13 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.20383.1> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.51755>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.20383.1>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},61170}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>},{<<"expect">>,<<"100-continue">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<
03:11
<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 1-Mar-2018::19:09:18 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.20388.1> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.51758>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.20388.1>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},61171}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>},{<<"expect">>,<<"100-continue">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
OK
03:12
O K
What % of network hashpower is one pool responsible for?
03:13
Deleted Account
did anyone get opencl miner to work..?
03:15
Deleted Account
In reply to this message
Yes, i have looked in Zack wallet and in mine and I dont see any balance in my wallet. Also now in yours but nothing appears. so who is this block owner? is there a place where i can see the list of blocks found with the miner who found it?
MH
03:17
Mandel Hoff
Amoveopool.com is up.
OK
03:19
O K
look how fast everything is moving again
03:19
😐
03:21
if you don't want the early success of amo to rely on one person, run your own nodes yeah?
D joined group by link from Group
03:22
Deleted Account
In reply to this message
block:all_mined_by(base64:decode("BLlLm4IM0yeIHwZgpa1Dte0d/FFW/V5kS+3nWDAr6EwYWcp+QXYS8BvTmquE4L61QdLFzyPZk4U+Tb2VBYcwZxE=")).


rp(block:all_mined_by(base64:decode("BLlLm4IM0yeIHwZgpa1Dte0d/FFW/V5kS+3nWDAr6EwYWcp+QXYS8BvTmquE4L61QdLFzyPZk4U+Tb2VBYcwZxE="))).
03:22
these will give you blocks mined by a node
03:23
returns [1,2,3,4,5,6,7,8,9,10,11,12,13,24,25,28,49,50,51,52,53,85,
86,108,110,119,120,136,151,152,194]
F
03:23
Francesco @ Simply
In reply to this message
no
OK
03:24
O K
network stuck again
03:25
Deleted Account
In reply to this message
did you install dependencies..?
03:26
Deleted Account
i’m at 204
03:26
pool is behind
03:26
Deleted Account
@scottmatheina and the other way round, with the block, where is the block? or how to know if a block has dissapear. i have this log "found work
44233163302257823508909331938396468211391070930403223092693707058275957537785" but i put your command or look in wallet and nothing appears. this work where is now?
03:26
Deleted Account
In reply to this message
Nothing wrong
03:27
might not exist
03:27
maybe didn’t count
03:27
what’s your address?
03:28
Deleted Account
it happens? you found a block and doesnt count? i was waiting 4 hours for a block and it doesnt count.. 😭
03:29
BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=
03:31
Deleted Account
rp(block:all_mined_by(base64:decode("BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg="))).
03:31
nothing... no blocks
03:31
you mined, but weren't at the top height maybe
I
03:31
Iridescence
If somebody mines a block ahead of you your block won't count
03:32
Deleted Account
i lost at least a hundred blocks that way.. node has to be at top height
I
03:32
Iridescence
If you mine block 195 but somebody else has already mines block 195 and 196, your block will not count
03:33
Deleted Account
if you mine 195, but your node doesn't or can't tell anyone else, then it won't count
I
03:33
Iridescence
Try sync_mode:normal().
03:34
Deleted Account
that was the issue before.. but today doesn't seem to be a problem if your node is setup correctly
03:34
Deleted Account
In reply to this message
thanks, good to know
I
03:34
Iridescence
I meant on the node
03:34
Yeah
MH
03:34
Mandel Hoff
Can't get my pool to sync back up... trying to fix.
03:35
Deleted Account
Just play with it. best way to learn and get a file with the commands from the github helps
I
03:35
Iridescence
block:height(). To check the height of the node
03:36
sync:start(). To start syncing
MH
03:37
Mandel Hoff
what is top height now?
OK
03:37
O K
206 at least
MH
03:37
Mandel Hoff
Ok, I have 206 on my pool.
03:37
207
03:38
It's a scramble to stay at top height. Going to be rough at 3am. 😱
03:39
Deleted Account
208
I
03:42
Iridescence
Who are your peers ? Type peers:all().
03:43
Ok seems good
03:43
api: height ().
03:44
Hmm
Z
03:44
Zack
In reply to this message
Yes. I already pushed a fix. This was because the headers were changed
I
03:44
Iridescence
sync:stop(). And then sync:start(). again
Z
03:45
Zack
In reply to this message
This is normal behavior I'd you don't have externally accessible port for Amoveo
I
03:45
Iridescence
Yeah
03:45
What is your IP?
03:46
Don't worry I won't ddos you 😜
Z
03:46
Zack
In reply to this message
We did a practice launch today to get ready for the main net launch. So everyone's balances started from 0.
03:47
In reply to this message
Yes. For main net everyone's balances will start at 0.
03:48
In reply to this message
Wrong. There is a new document about syncing. Look in the getting started folder.
03:49
In reply to this message
I don't see the problem. Is that not all the blocks?
03:49
In reply to this message
False. It does not change modes automatically.
03:50
Deleted Account
headers 224 blocks 220.. node trying to get blocks but failing
Z
03:51
Zack
In reply to this message
Great. Thanks for testing Scott
03:53
In reply to this message
Change to sync_mode normal.
I
03:54
Iridescence
In reply to this message
Your node is reachable so that's not an issue
Z
03:54
Zack
In reply to this message
I think no one but me got it to run.
03:54
In reply to this message
Sounds like a cool tool to make. Let's compare the pools and make a chart in the browser.
I
03:55
Iridescence
Block height is 230 now
Z
03:55
Zack
In reply to this message
Yes. The Explorer.html that each of us hosts, or Mandel s page. Amoveo pool
03:55
Deleted Account
i have headers of 230 but blocks 220
Z
03:56
Zack
In reply to this message
Great. Thank you for supporting the other users Scott.
03:56
In reply to this message
Looks normal. Follow the directions in the README.
03:58
In reply to this message
This is not working. It isn't connected to a node or pool.
03:59
Deleted Account
looks like my node is trying it's darndest to get those blocks, but not happening
Z
04:00
Zack
In reply to this message
If you do not have externally accessible IP address, then it cannot sync blocks automatically.
I
04:01
Iridescence
His node is externally accessible
Z
04:01
Zack
In reply to this message
Someone might be mining wihout sharing blocks again. This happens if they don't have externally accessible IP address
I
04:02
Iridescence
I checked by querying his node
Z
04:02
Zack
In reply to this message
Cool. Thanks
04:02
Deleted Account
i did sync stop and start and not fixed..so I'm going to let it go for a while and see if it fixes itself
04:03
I'm getting headers, I know I'm ok
I
04:03
Iridescence
My node is synced. 232 now
Z
04:03
Zack
I see 232 headers and 232 blocks
04:04
Deleted Account
tial block died!block:height().potential block died!
220
(amoveo_core_prod@anode)15> potential block died!many headers [-6,1001,112]
many headers [-6,1001,1112]
potential block died!tx_pool_feeder died
could not get block 450 from peer [-7,[-7,199,247,26,222],8080]syncing with this peer now [-7,[-7,209,250,248,93],8080]
trade peers
get their top header
my block height is less than theirs
another get_blocks thread
another get_blocks thread
potential block died!another get_blocks thread
another get_blocks thread
another get_blocks thread
potential block died!api:height().
232
Z
04:06
Zack
In reply to this message
I have still not solved the "potential block died" problem.
As long as it is happening you will not be able to mine.
if you turn off and on, it goes away.
04:06
Deleted Account
ok I'll restart
Z
04:07
Zack
you can keep your blocks even
04:09
In reply to this message
actually, I thnk you need to get rid of the blocks.
04:09
Deleted Account
yep.. didn't help
04:09
purging blocks
04:12
I'm back
Z
04:12
Zack
yes, I just did the same. I am looking through logs to try and solve this issue.
04:17
it is supposed to be the case that only the tree_data gen_server can modify the tries on your hard drive.
I think maybe one of the other processes edited a trie at the same time, and the 2 edits got mixed up so the tree data became invalid.
04:30
Deleted Account
I am in the top heigh 254, but i have found another work and the balance does not change. is normal?
Z
04:31
Zack
In reply to this message
are you BLILm...?
04:32
Deleted Account
In reply to this message
what do you mean? the three blocks i have found didnt count, is it normal o could be smth wrong in wallet config?
Z
04:33
Zack
BLILm..... is the address that found 254.
04:33
Deleted Account
no, theses blocks were 20 mintus ago, 66528786074321970286920812666776753274346928255507333485620762660789514752972
67208242648638910494564473897151040865222308325676918226640969973436597906025
Z
04:33
Zack
so what is your address?
04:33
those are nonces. I can't do anything with them.
MH
04:34
Mandel Hoff
To anyone using my pool:
I will do my best tomorrow to keep the pool alive. For Day 1, I will probably make confirmed block delay a few blocks longer depending on the difficulty. This will not reduce your payout, but it will delay it by a few blocks.
04:34
Deleted Account
how do you know BLILm , is there any command to know the block and the address? BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=
Z
04:34
Zack
the explorer says so http://159.89.106.253:8080/explorer.html
04:35
Deleted Account
oohh good!! it was what i was looking for. Thanks
Z
04:35
Zack
In reply to this message
you have mined zero blocks.
If you are not fully synced while mining, then you cannot find blocks.
04:36
Deleted Account
always i have tested api:heigh i am on top, i dont know if i didnt get on top for few seconds
Z
04:37
Zack
api:height says your headers. you need blocks to be fully synced too. block:height().
04:37
Deleted Account
ok, alwsy says the same for me, 256 now
Z
04:38
Zack
yes I am on 256 too
04:38
Deleted Account
how the explorer works? i write the block 67208242648638910494564473897151040865222308325676918226640969973436597906025 and look for it and does not show anything
Z
04:38
Zack
that is nonce. you can't do anything with a nonce.
04:39
where it says "block number", put the height of the block you are interested. the block number of the recent block is 256.
04:40
Deleted Account
ok, so how i know if a nonce has been rejected? only bc my balance doesnt change?
Z
04:41
Zack
I don't know what "nonce has been rejected" means.
You can look up who mined which block in the explorer. there is also a command to look up all the blocks you have mined from your hard drive.
04:41
block:all_mined_by(Address).
04:45
Deleted Account
I thought that when i have the following log:found work
67208242648638910494564473897151040865222308325676918226640969973436597906025
it was a block found
Z
04:45
Zack
yes, that means you found a block.
04:45
but the block you found might not get included in the chain.
04:45
Deleted Account
and as Zack explain to me somtimes it does not count bc i am not in the top
Z
04:46
Zack
or if you fail to tell anyone else about it
04:46
like if you don't have externally accessible ip
MH
04:46
Mandel Hoff
In reply to this message
Zack - this pool death happened twice now. I recovered but had to do the "kill all erlang" script and restart node/pool.
04:48
Deleted Account
so the Three i have found has fail, but how i know why? Now i was looking to be synced but anyway it doesnt count. ip access yes bc it is a vps with static ip
Z
04:48
Zack
In reply to this message
yes, this is concerning. can you share the crash.log from the amoveo full node?
04:48
In reply to this message
so what is the url for your explorer?
04:49
Deleted Account
http://209.250.248.93:8080
Z
04:49
Zack
http://209.250.248.93:8080/explorer.html
looks like you are synced up
04:49
Deleted Account
yes
Z
04:50
Zack
I guess you were just unlucky, and someone else found a block about the same time as you, all 3 times.
04:51
Deleted Account
In reply to this message
i am mining to a local mining pool with two miners. it seems to be good configured
Z
04:51
Zack
In reply to this message
oh that is why.
You need a mining pool if you are using more than one miner
04:51
I will update the docs to explain about this.
04:51
Deleted Account
In reply to this message
yes i have it
Z
04:51
Zack
thank you for asking all these questions, this is important to explain correctly
04:52
Deleted Account
In reply to this message
i have the mining pool and mining to my mining pool with two miners, one in the same machine and the other in other machine
04:53
both 0,6-0,8 mhs only for testing
MH
04:53
Mandel Hoff
In reply to this message
This is from the erlang pool log:
["recent_work","FTMQBistvBs2bNvhmwovHekTirsNLGmJIdsdVtbcMyA=",8332,47202329466298674686535206952541611434438822921920519036546117592458110633182]^M
["recent_work","ZiE9Hcf/FDx7OmyZCN0WizYm1N7TSbiSa7pje8ee36M=",8332,50407808385826406755024775220931416538809163538645061311034224277551147655060]^M
["recent_work","kHNTVrDSNsWnytFdMqJxIW0oY6S1r+6qwNtzbShlhpU=",8332,18181290546306049101931289846580313770994813315229359319746870829431240089525]^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]^M
=ERROR REPORT==== 1-Mar-2018::19:32:00 ===^M
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.594.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.1167>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.594.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},63133}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>},{<<"expect">>,<<"100-continue">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]^M
first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]^M
=ERROR REPORT==== 1-Mar-2018::19:32:05 ===^M
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.612.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.1182>},{transport,ranch_tcp},{connection,keep
04:53
In reply to this message
alive},{pid,<0.612.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},63152}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>},{<<"expect">>,<<"100-continue">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]^M
first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode ^M
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]["recent_work","dPax9INgaOoyVCjS704P2ah9j/SHrAXT52yzwAxLeL4=",8332,36988454201493819904375192899372392309128072449952150308006355169610951034147]^M
Z
04:54
Zack
In reply to this message
make sure both miners are connected to the pool, and neither connects directly to the amoveo full node
04:55
In reply to this message
I was asking about the amoveo full node crash.log actually.
04:55
It is clear that the pool is unable to connect
MH
04:55
Mandel Hoff
Yes, that was almost empty. Just this:
2018-03-01 19:26:07 =ERROR REPORT====
** Generic server block_absorber terminating
Z
04:55
Zack
now we want to know why it cannot connect
MH
04:55
Mandel Hoff
The node seemed fine - just the erlang pool was in a bad state.
Z
04:56
Zack
hmmm... that makes it difficult.
04:56
Deleted Account
In reply to this message
in miner.erl once is -define(Peer, "http://209.250.248.93:8085/" and the other is localhost... and when i restart the node both miners get unatached and when it recovers it attached again mining
04:57
Zack first Mandel, his problems affects more people
MH
04:58
Mandel Hoff
I can recover when I notice this occurring. No rush, but thank you.
Z
05:00
Zack
In reply to this message
so you have it set up incorrect. make sure both are connected to :8085
otherwise it wont work.
MH
05:01
Mandel Hoff
05:01
Deleted Account
In reply to this message
i am conected, if i stop the node it stops mining, if i start the node it reconects mining. somehting else to configure?
MH
05:01
Mandel Hoff
12 hour bandwidth looks really good - just reporting. No complaints at all there.
Z
05:03
Zack
In reply to this message
great
05:04
In reply to this message
you said you have 2 miners right?
make sure both are connected to the mining pool on port 8085. don't connect either to the full node.
05:05
Deleted Account
yes yes, they are
05:05
In reply to this message
they are to "http://209.250.248.93:8085 and "http://localhost:8085
Z
05:06
Zack
then I guess you have just been unlucky. everything is set up correctly.
05:07
Deleted Account
ok, if i am unluky ok, but i wouls like to know everything is ok configured
05:17
In reply to this message
i have just found a block and the balance changed. i was unluky. Thanks Zack
Z
05:18
Zack
great
05:21
looks like 2 people found blocks 281. I bet Mandel's pool will win the fork.
05:22
yes, Mandel's pool won.
05:23
Deleted Account
How could be : http://159.89.106.253:8080/explorer.html the block 274 was mined by BLlLm4IM0yeIHwZgpa1Dte0d/FFW/V5kS+3nWDAr6EwYWcp+QXYS8BvTmquE4L61QdLFzyPZk4U+Tb2VBYcwZxE= and http://209.250.248.93:8080/explorer.html block 274 was mined by BPFuy9IF7xKGyYwmedCNuY+epxKnzdK/UoUCmpasD366l3sttKyERyR2daHlaxc8IrzVEajSGwI3YL9VZrhbMsg=
Z
05:25
Zack
In reply to this message
209.250 is a frozen node.
05:25
Deleted Account
ok, thks
Z
05:25
Zack
it is unable to download blocks from the rest of us
05:25
it is on a small losing fork.
MH
05:34
Mandel Hoff
Yuck - my downloads folder has 100+ private keys. I'll probably just most of my veo due to mismanaging my keys.
Z
05:36
Zack
In reply to this message
Haha. Maybe we need a tool to sort keys
MH
05:37
Mandel Hoff
I have no idea what would be ideal key management, but I need to clean house on my accounts.
05:40
I got a kick out of my AVG antivirus. It said my mining tool was "rare software" and a copy was sent to their labs for analyzing. 😂
Z
05:42
Zack
haha. hopefully they approve it soon so more people can mine
MH
05:46
Mandel Hoff
Not sure. I think they label minerd and ccminer as malware, because they get packaged in a lot of botnets. Not sure how it'll get classified.
Z
05:47
Zack
then our mining software will end up in botnets pretty soon too
MH
05:49
Mandel Hoff
Probably, but it's not like monero's hash. Sha 256 is very fpga & asic friendly. Botnets won't bother. They'll stay with monero.
Z
05:49
Zack
yes, that sounds right
MH
05:52
Mandel Hoff
I'm probably moving all my monero over to amoveo tomorrow. Network difficulty on monero is so high that it's not fun anymore.
06:00
Deleted Account
is there anyway to deatach /atach a c_miner? and is there any way to automate the miner lunch? make a services or smth to start automatically on restart?
06:01
Deleted Account
potential block died! , looks like my node died again
06:02
Deleted Account
T minus ???
G
06:02
Gonzalo
All my 3 nodes api:height 319, but block:height are at 231, 231 and 224. Is this ok?
MH
06:03
Mandel Hoff
I wish "Bankers" would come back out and play. I'd love to speed test the back and forth some more.
06:03
Deleted Account
This is going to be epic. First crypto I witness from launch.
G
06:05
Gonzalo
Mandel I asked before but havent seen your answer, sorry. Do you know if your Ubuntu miner will work on Debian?
06:06
In reply to this message
13 hours
MH
06:06
Mandel Hoff
Sorry, no clue. Probably yes, but not sure. RestCPP says it works on Debian:
https://github.com/Microsoft/cpprestsdk
06:06
Deleted Account
Damn it, that's 5am my time
MH
06:07
Mandel Hoff
Crypto never sleeps. 👍
G
06:07
Gonzalo
In reply to this message
nice, thanks, Then I'll give it a try and I'll tell you.
06:08
Deleted Account
In reply to this message
That's the beauty, and launch is quite monumental to miss.
MH
06:10
Mandel Hoff
Status: Pool is back to 1gh/s and I'm not mining.
06:11
Deleted Account
1gh? That's huge Is it not?
06:11
1000mh
MH
06:12
Mandel Hoff
Yes, but not really for sha256.
06:12
Deleted Account
Well, it is for CPU only
MH
06:12
Mandel Hoff
Someday, 1gh/s Amoveo would be <1 Asic or fpga.
06:13
Yes, that's pretty great for cpu only.
06:13
Deleted Account
Yeah, some day.
06:15
Ok, where can I lease 10000 CPU for 10 hours? 😂
MH
06:21
Mandel Hoff
Need to be away for a while. Back later.
06:24
Deleted Account
i had to restart my node again..
06:24
digital ocean
06:24
that would cost you
Z
06:27
Zack
In reply to this message
Not yet. These are good suggestions.
06:28
You can use screen to do this.
06:29
In reply to this message
your nodes lost consensus.
06:30
Deleted Account
In reply to this message
Zack Why do you said 209.250 is a frozen node?, It could explain lot of things to me. it is my node. i have rstart bc i got staked in block 274 the one i was suppose to found (make prod-clean, prod-restart sync start sync mode normal) and i have lost my balance. I am in a frozen node? how to change to a norma node?
Z
06:31
Zack
I read online that most CPU today have some dedicated space for sha256.
Maybe someone is using this to mine.
06:31
In reply to this message
looks like you are synced up with us now
G
06:32
Gonzalo
In reply to this message
Ok, any idea to solve this?
06:32
Deleted Account
but i have lost my balance and i dont know why. If i make prod-clean i loose my balance?
Z
06:33
Zack
In reply to this message
Maybe this was from the random number generator bug I fixed.
api:off().
halt().
git pull
make prod-clean
make prod-restart
06:34
In reply to this message
make prod-clean does not delete your keys.
06:34
Deleted Account
yes, but it was several hous ago... i have reset many times and this time has sync?
Z
06:34
Zack
In reply to this message
yes, you look like you are synced to me
06:34
Deleted Account
could be... and this explain i didnt get blocks?
Z
06:36
Zack
I feel like there is a language barrier here.
When you are "synced with the blockchain", that means you have downloaded and verified all the blocks, and you have computed the current state.
06:40
Deleted Account
yes first sync untill all blocks are donwload and then "normal". What i dont understand is how my balance was 1.0003xxx for a period of time for having found the 274 block if i didnt really found it. Now with the last restart i have sync the real blocks and none is mine so balance logically disappears, but where was my node when my miners found the block and the balance was increased? sorry so many question i dont understand
Z
06:48
Zack
In reply to this message
the sequence of blocks makes up a history. there was a fork with 2 alternative time-lines.
The network decided to use the time-line where you didn't mine the block.
06:49
at first your node was on the time-line where you won. so it displayed that you won.
Then later, you switched to the time-line where you lost.
06:49
This is why in bitcoin you cannot spend coinbase rewards for 100 blocks.
06:55
Deleted Account
In reply to this message
Thanks for the explanation. what is not clear for my is why i got stucked in the other time-line and if this situation could happen again during mainet. If so how we can pass the rewards from a time-line to the new one?
Z
06:58
Zack
In reply to this message
Ethereum pays the miner of orphaned blocks the way you describe.
It is complicated, and it can cause bad failure modes.
So I decided not to do that.
Amoveo is for oracles and turing complete state channels, so all my decisions were made based on this goal.
06:59
bitcoin does not pay the miners of uncle blocks. And bitcoin is doing fine.
07:00
12 hours until mainnet
07:00
Deleted Account
yes, i understand not all the balance got in the last timeline is lost, only the balance that was generated during desyncronization
07:00
Thanks.
07:02
Deleted Account
ok so I hadn't even tested the light wallet yet... and created a new wallet, and kept the key offline for mainnet... we'll I"m trying to more my testnet fund from my current wallet to this new one to test the light wallet.
07:02
well I'm trying to move and not sure what's up..
07:02
i tried several times to move and wait for a block or 2 to pass, but my funds are still in my old wallet
Z
07:03
Zack
https://github.com/zack-bitcoin/amoveo/blob/master/docs/api/commands_accounts.md
The current documentation could probably be improved.
tx_pool:get(). gives you a list of txs in your mempool
07:12
Deleted Account
my node died for the 3rd time this afternoon
07:12
potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!tx_pool_feeder died
potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!potential block died!syncing with this peer now [-7,[-7,51,15,212,91],8080]
trade peers
get their top header
potential block died!potential block died!syncing with this peer now [-7,[-7,159,65,197,154],8080]
trade peers
get their top header
already synced with this peer
potential block died!potential block died!syncing with this peer now [-7,[-7,159,65,197,154],8080]
trade peers
Z
07:13
Zack
yes, I have seen this potential block died error. I am working on it. but I still haven't identified the cause.
07:24
I found and fixed a bug that was causing us to freeze sometimes.
It was different from the potential block died! bug.
07:31
Deleted Account
In reply to this message
thanks.. it eventually went through
07:31
took a couple blocks
Z
07:32
Zack
In reply to this message
great
07:44
Deleted Account
cool. I was able to send from light wallet old account to new account, back to node, and then back to another account.. you just need to wait for the confirmations
Deleted joined group by link from Group
08:09
Deleted Account
what is the starting difficulty and how quickly will it adjust
08:09
howmuch hash rate is expected for the first difficulty phase
08:11
Deleted Account
In reply to this message
i was lucky for days 😎
Z
08:12
Zack
In reply to this message
great
08:13
In reply to this message
about 6.6 gigahashes.
It retargets every 2000 blocks to try and make 10 minutes per block.
08:18
Deleted Account
and the reward is 1 veo?
Z
08:19
Zack
In reply to this message
it starts at 1 VEO, but the community can change it.
08:19
Deleted Account
right, same with block time. I'm not sure how to change it though
Z
08:20
Zack
In reply to this message
https://github.com/zack-bitcoin/amoveo/blob/master/apps/amoveo_core/src/consensus/txs/test_txs.erl#L596
Here is a test showing the steps to update a governance variable.
08:52
Deleted Account
tx_pool_feeder died this is filling my terminal window right now
08:52
miner seems to be working though
Z
08:52
Zack
In reply to this message
that means you downloaded invalid txs from someone.
08:53
Deleted Account
ok.. yah whoever you are. stop giving me bad transactions!!! lol
08:53
ok my node just died.
08:53
:(
08:55
prod-blocks invalid command now
Z
08:55
Zack
In reply to this message
yes. it deletes the blocks with prod-clean.
08:55
Deleted Account
ok thanks
08:57
ok back online
OK
09:16
O K
What are all known pools that will be active at launch?
09:19
Deleted Account
http://192.241.144.151:8080 anyone can use my node...
Z
09:20
Zack
browser mining is pretty slow, but it does work
09:20
Deleted Account
default fee, but keeps you from dealing with the node updates
09:21
thanks to zach's hard work, it's an update every hour!!
M
09:30
Minieep21
Anyone got a pool setup?
Z
09:31
Zack
In reply to this message
yes, there are 2. read 5 comments above
M
09:33
Minieep21
Ah sorry, stayed up late to get this setup 😂
Deleted invited Deleted Account
M
09:36
Minieep21
Hmm amoveopool.com not opening
Z
09:38
Zack
In reply to this message
yes, I agree.
09:38
and his pool stopped making blocks. I think all the blocks are coming from Scott now.
09:41
Deleted Account
YES!!!!!
09:41
My day has come!
Z
09:41
Zack
haha
09:41
Deleted Account
yah, i saw that
MH
09:44
Mandel Hoff
Ugh, erlang pool died again:
09:44
=ERROR REPORT==== 2-Mar-2018::01:43:56 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.3556.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.3760>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3556.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},50422}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 2-Mar-2018::01:44:01 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.3560.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.3764>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3560.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},50426}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 2-Mar-2018::01:44:06 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.3563.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,
09:44
"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.3767>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3563.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},50427}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 2-Mar-2018::01:44:11 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.3566.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.3770>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3566.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},50428}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 2-Mar-2018::01:44:17 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.3570.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/htt
09:44
p_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.3774>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3570.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},50469}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]first failure mode
cannot connect to server[-6,104,116,116,112,58,47,47,108,111,99,97,108,104,111,115,116,58,56,48,56,49,47]["mining_data"]
=ERROR REPORT==== 2-Mar-2018::01:44:22 ===
Ranch listener http had connection process started with cowboy_protocol:start_link/4 at <0.3574.0> exit with reason: [{reason,{timeout,{gen_server,call,[mining_pool_server,problem]}}},{mfa,{http_handler,handle,2}},{stacktrace,[{gen_server,call,2,[{file,"gen_server.erl"},{line,204}]},{mining_pool_server,problem_api_mimic,0,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/mining_pool_server.erl"},{line,48}]},{http_handler,handle,2,[{file,"/home/litepro2/amoveo-mining-pool/_build/prod/lib/amoveo_mining_pool/src/http_handler.erl"},{line,9}]},{cowboy_handler,handler_handle,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_handler.erl"},{line,111}]},{cowboy_protocol,execute,4,[{file,"/home/litepro2/amoveo-mining-pool/_build/default/lib/cowboy/src/cowboy_protocol.erl"},{line,442}]}]},{req,[{socket,#Port<0.3777>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.3574.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{23,96,187,38},50506}},{host,<<"52.234.133.196">>},{host_info,undefined},{port,8085},{path,<<"/">>},{path_info,undefined},{qs,<<>>},{qs_vals,undefined},{bindings,[]},{headers,[{<<"content-type">>,<<"application/json">>},{<<"host">>,<<"52.234.133.196:8085">>},{<<"content-length">>,<<"15">>}]},{p_headers,[]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,false},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,undefined}]},{state,no_state}]
Z
09:45
Zack
In reply to this message
This just says that the full node would not respond.
09:46
I rewrote the syncing code again. I refactored it to remove some repetition, and I significantly reduced the bandwidth requirements.
MH
09:46
Mandel Hoff
Full node just spamming this:
09:47
09:47
I'll turn off my node and update.
Z
09:47
Zack
yes, this is a known failure mode. I am still not sure what causes it.
It seems like the trees database must be getting corrupted somehow.
09:48
because it says stuff about the data in the trie forming invalid merkel proofs
Deleted invited Minh Truong
MH
09:50
Mandel Hoff
Did you pick a main net launch initial diff?
Z
09:50
Zack
I was thinking of having it the same as today
09:51
Deleted Account
if we find blocks too fast, then it would just reset sooner. so I'm game
MH
09:53
Mandel Hoff
Amoveopool.com is alive now. Sorry for the downtime.
M
09:56
Minieep21
In reply to this message
Thank you! Set up the CPU miner :)
Z
09:56
Zack
Before this update, if you needed blocks, you would alway download the 20 most recent.
Now you ask for their headers, and you use the headers to calculate exactly the blocks you need, so you don't download extra.
MH
09:56
Mandel Hoff
I'm partly for low diff, because I'll benefit - but, I think a much higher diff might be good for the network. It'll raise after 2k blocks too, which we'll probably do in under 1 day at current diff.
09:58
As long as the network stays up, I think we'll do 2k blocks tomorrow at the current diff.
Z
09:58
Zack
yes, a block per minute seems a little fast. and there will probably be even more miners tomorrow
09:59
Deleted Account
we could probably do 4x the diff and still be low.. but I"m good regardless
Z
09:59
Zack
in the long run, 2000 blocks don't matter very much
09:59
Deleted Account
nope it'll go very fast
MH
09:59
Mandel Hoff
Yes, I barely mined today and I think I can double my pool's hashrate from today. I'll be mining in to amoveopool.com, so easy to monitor
10:00
Agreed, 4x diff will still be fast blocks tomorrow.
Z
10:01
Zack
ok, ill raise the difficulty 4x
MF
10:02
Mr Fox
main launch ?
Z
10:03
Zack
In reply to this message
9 more hours
MF
10:03
Mr Fox
Sticker
Not included, change data exporting settings to download.
👍, 13.8 KB
I
10:03
Iridescence
so what will be the difficulty for mainnet launch?
Z
10:04
Zack
probably around 24 gigahash per block
MH
10:04
Mandel Hoff
About 25billion diff if it's 4x today
I
10:05
Iridescence
Funny how you guys use different measures of difficulty
10:05
and I use different ones as well
10:05
I think in terms of the difficulty as mentioned in the amoveo code
10:05
hash2integer
10:07
Deleted Account
all the mining is going to be pretty worthless at 1 veo per block, because governance is almost definitely going to gravitate toward high supply for awhile
Z
10:07
Zack
In reply to this message
That is something very difficult to predict.
MH
10:08
Mandel Hoff
Please explain why would governance vote for inflation.
I
10:08
Iridescence
why high supply?
10:09
speaking of governance, how is that weighted by?
Z
10:09
Zack
If the initial block reward was 50 or 25 or 0.5, it doesn't make a difference.

The size of the block reward only has meaning in relation to the total market cap. At the beginning the market cap is zero, so every sized block reward is the same.
10:09
Deleted Account
because buyers are known to prefer low value coins, regardless of market cap. So if the goal is to increase the market cap this would be done by increasing the miner reward in coins, which means early miners getting 1 per block will lose efficiency
I
10:10
Iridescence
I see, and governance will set the market cap
10:10
or rather, supply cap
10:10
Deleted Account
it matters in a way, because if the initial reward was 1 billion coins, then the low-price coin anomoly would get taken out immediately, and people would then prefer no more inflation
Z
10:11
Zack
Amoveo erlang code doesn't know what a VEO is, it only uses Satoshis.
It is completely up to the wallet to decide how many Satoshis makes one token.
We could move the decimal place over in the wallet, if that would be preferable.
10:11
Deleted Account
Yeah i suppose thats true
10:11
it will be interesting to see
MH
10:11
Mandel Hoff
"Buyers are known prefer low value coins". Sounds like that's the basis for your argument. I'm not sure I accept that assumption, but I'm not arguing it's incorrect either.
10:12
Deleted Account
i know its weird, but its been looked at. Its not logical but a lot of buyers right now are not savy, so they end up buying stuff like ripple just because its $1 instead of $10000
10:12
so low priced coins have unwarranted excess demand
10:13
which in a system like amoveo means the governance will graviate towards low price coin
I
10:13
Iridescence
I don't think such investors know about Amoveo yet...
G
10:13
Gonzalo
In reply to this message
its sad but this is true
10:13
Deleted Account
those investors dont need to know about amoveo though
Z
10:13
Zack
I think we should make 1 token be worth $100,000. That way we can avoid those kinds of investors.
10:13
Deleted Account
sounds good to me
I
10:14
Iridescence
😂
Z
10:14
Zack
So the initial block reward should be like 0.0001
I
10:14
Iridescence
so 10 VEO = millionaire?
10:14
just have to mine 10 blocks 😂
MH
10:14
Mandel Hoff
Anyone want some free test net veo? Last call! 🙈
Z
10:15
Zack
In reply to this message
BCjdlkTKyFh7BBx4grLUGFJCedmzo4e0XT1KJtbSwq5vCJHrPltHATB+maZ+Pncjnfvt9CsCcI9Rn1vO+fPLIV4=
10:16
Deleted Account
if the inflation stays the same, but the price is tied to the cost of the network hash, that may be a reasonable way to approach this
MH
10:16
Mandel Hoff
I'm going to crush all of you mining, and then I'm going to lose all my veo betting on horrible things in the first derivatives market that is opened and be broke.
G
10:16
Gonzalo
In reply to this message
Yeah! Send them to my BITCHx33q94k90RGFb2LgcFnZxalgT9djGA550jgrIR5E6iqo6TEBl3UMUz2OOr8firoejaptuOf+gEIGDgT+bg=
10:16
Deleted Account
how is it determined who receives compensation in the developer reward
M
10:16
Minieep21
In reply to this message
Good luck.
I'm gonna connect my uni PC lab to your pool
Z
10:16
Zack
In reply to this message
It is better to make a market, that way your money can only grow. let other people bet
10:17
In reply to this message
it only goes to me
MH
10:17
Mandel Hoff
Actually, that Bankers person will probably crush all of us tomorrow, so don't take my previous comment too serious.
10:17
Deleted Account
i will buy people's veo, just PM if you are looking to sell
MH
10:18
Mandel Hoff
In reply to this message
This is a governance variable set ~16% to your private address still for main net, right?
Z
10:18
Zack
In reply to this message
https://github.com/zack-bitcoin/amoveo/blob/master/docs/use-cases-and-ideas/insured_crowdfund.md
The long term plan is to turn off the developer reward and use dominant assurance contracts instead.
10:18
Deleted Account
yeah i read about dominant assurance contracts
10:18
that is an interesting concept that id like to try out
Z
10:18
Zack
In reply to this message
cool
10:19
Deleted Account
As far as Im aware no coin has solved compensation for contributors
10:19
the closest I have seen is DPoS, which is unfair to a lot of participants
Z
10:20
Zack
In reply to this message
I can't remember what it is set to at the start. ill check.
MH
10:20
Mandel Hoff
I agree there's alot of broken models, but I think "Solved compensation" is too subjective to have a solution that everyone would agree upon.
10:20
Deleted Account
the assurance contracts seem good to me
MH
10:20
Mandel Hoff
In reply to this message
I almost don't care what it is. You deserve whatever you want to take from the pot.
10:20
Deleted Account
but im not completely sure how all partipants in the system are "forced" to participate
Z
10:21
Zack
looks like 16%, you were right
10:21
1/6th
MH
10:21
Mandel Hoff
Ok, so no change since test net then. Good to know.
G
10:22
Gonzalo 
amoveouser@amoveo-scaleway-03:~/amoveo$ make prod-restart
===> Verifying dependencies...
===> Skipping pink_hash (from {git,
                                      "https://github.com/BumblebeeBat/pink_crypto",
                                      {tag,"master"}}) as an app of the same name has already been fetched
===> Compiling amoveo_http
===> Compiling amoveo_core
===> Starting relx build process ...
===> Resolving OTP Applications from directories:
          /home/amoveouser/amoveo/_build/prod/lib
          /home/amoveouser/amoveo/apps
          /usr/lib/erlang/lib
          /home/amoveouser/amoveo/_build/prod/rel
ok
===> Resolved amoveo_core-0.1.0
===> Including Erts from /usr/lib/erlang
===> release successfully created!
make[1]: Entering directory '/home/amoveouser/amoveo'
Node is not running!
Makefile:144: recipe for target 'attach' failed
make[1]: *** [attach] Error 1
make[1]: Leaving directory '/home/amoveouser/amoveo'
Makefile:279: recipe for target 'prod-restart' failed
make: *** [prod-restart] Error 2
Z
10:22
Zack
In reply to this message
do make prod-attach
G
10:22
Gonzalo
FYI, this happened after git pull + make prod-restart
Z
10:22
Zack
the attach step of the script failed because the app wasn't open yet
G
10:23
Gonzalo
ok thanks
10:23
Deleted Account
in the breakout of entrepreneurs, investors, and builders, it seems that some investors can choose to stay passive and still benefit when the builders are funded
Z
10:23
Zack
I increased the delay between opening the app and attaching, but I guess I should increase it a little more
10:23
Deleted Account
In reply to this message
Yes Yes Yes
Z
10:24
Zack
In reply to this message
investors and entreprenuers are both doing passive investments
G
10:24
Gonzalo
In reply to this message
This is the first time I see this
10:24
I just did build + go + attach
Z
10:24
Zack
In reply to this message
https://github.com/zack-bitcoin/amoveo/blob/master/Makefile#L279
see it sleeps 3 seconds between go and attach
10:25
so it has time to start up the app
10:25
make prod-restart automatically waits 3 seconds
G
10:25
Gonzalo
ok nice
10:27
ok, Im going to sleep for a while, so thanks Zack and good luck tomorrow to everybody 👍
10:29
Deleted Account
here's another logo concept (this i just found online)
10:29
10:29
looks like an A, M, and V, so i kinda like it... doesn't have any motifs though
10:29
Deleted Account
how long would a miner take to solve diff = 8332 on a single cpu thread?
Z
10:30
Zack
In reply to this message
cool
I
10:30
Iridescence
looks like WaltonChain color scheme
10:30
Deleted Account
i mean, we cant use this logo because its probably already somebody elses, but we can get something designed thats similar, and pick cooler colors
Z
10:31
Zack
In reply to this message
with my computer at 0.17 mh/s it would take like 100,000 seconds which is like 1 day.
I
10:31
Iridescence
Zack you should sell some VEO and buy a better rig
Z
10:31
Zack
I think we should wait till we have our first community of users for the smart contract, then we should rebrand after looking at them and how they use Amoveo
10:32
maybe we will even rename it at that point.
MH
10:32
Mandel Hoff
In reply to this message
👍 I hope he gets crazy rich of this whole game. Toys for Zach.
10:32
Deleted Account
In reply to this message
oh wow.. thx. I'm just trying to solve it to compare the results with the GPU miner. since the gpu miner is exiting right away with an invalid result