We need to provide the public key (or alias) of the target node that we'll be trying to attack for ln_10 and ln_100 (since this is based off the real graph, we need to map from the node we picked IRL to the graphs we've generated). IIRC the id in our graphml file is just the index as nodes appear in graph.json so it should be easy to grab the right alias.
~Since pubkeys will be different each run, we should think about adding a nice utility in the run script that'll identify the pubkey (or provide it manually like we do for connection details for lightning nodes).~ Done!
We need to provide the public key (or alias) of the target node that we'll be trying to attack for ln_10 and ln_100 (since this is based off the real graph, we need to map from the node we picked IRL to the graphs we've generated). IIRC the
idin our graphml file is just the index as nodes appear in graph.json so it should be easy to grab the right alias.~Since pubkeys will be different each run, we should think about adding a nice utility in the run script that'll identify the pubkey (or provide it manually like we do for connection details for lightning nodes).~ Done!