Congrats on successfully installing PeerChat! Let us know your experience. How’s the speed? Do you see other chat rooms?
Speed is fine, I don’t see other chat rooms or anyone online, but I do see conversations I’ve started that persist after reboot.
Great to hear, thanks for the update Peter! Woohoo!
I’m trying to start 0.0.4 on a mac. The start screen appears for some short seconds and then disappears. Then, nothing. The tray icon is there but no more action.
I ran the 0.0.3 version successfully, maybe I should clear all data from previous install and start fresh?
Where should I clean out the old app data?
EDIT: Forget about 0.0.4. 0.0.5 runs fine through nix-shell following the instructions on GitHub - holochain/holoscape: A complete end-user deployment of a Holochain conductor with UI for administration and a run-time for hApp UIs
Nice work! 
3 Likes
Great! Although 0.0.5 is not yet released, but almost 
So you basically got the release candidate from source.
The data is in XDG compliant user directories. On macOS that would be ~/Library/Application Support/Holoscape-default.
And yeah, general statement about the UX of <=0.0.4 and the lack of a main window, that is fixed with a major UX revamp coming with 0.0.5. You could also try running it from source, @petersgrandadventure, as @kristofer did, or wait until the next binary release. There were a few last minute fixes, but I really want get it out tomorrow!
1 Like
@lucksus I guess there isn’t time for more features before the release of 0.0.5? For future releases, one thing that would be Great is the ability to detach console / devtools to a separate window. Currently the console ends up below the content of the hApp which makes debugging really hard. I also get a sense that the console is not picking up output from the indivudual hApps, but it is difficult to really tell since the view is mostly hidden.
EDIT: Managed to detach devtools, menus are clickable first time window appears. But as I suspected, console output is not from hApp but from Holoscape only. Is there a way to open devtools for an indiuvidual hApp?
(ps. I’m having difficulties with the settings, connecting my local hApp with the DNA, the UI instance etc. It seems don’t get a reply from /_dna_connections.json)
2 Likes
Is this currently possible? If so, where do I open the bundle file from Holoscape? I’ve managed to install by editing the config files manually but would like to try with the bundle as well.
@lucksus, I saw the menu item to install local bundles reappeared. Great, thanks! Tried to install bundle. Almost worked.
No [[interfaces.instances]]is created and the port number for the driver is the same as another hApp.
bundle.toml:
bridges = []
[[instances]]
name = "holotxt"
id = "holotxt_instance"
dna_hash = "QmP8hH9rF2RBsKX8dZSC6eZcHkq6XhgsFjHN3pC24KWH1R"
uri = "file:./holotxt_dna/dist/holotxt_dna.dna.json"
[[UIs]]
name = "Holo.txt"
id = "holotxt_id"
ui_bundle_hash = "Qm34abcde"
uri = "file:./holotxt_ui/gui.zip"
[[UIs.instance_references]]
ui_handle = "holotxt"
instance_id = "holotxt_instance"
Perhaps I misunderstood some detail in the bundle file?
Hey, @kristofer, thanks for the hint regarding the dev tools. That actually did make it into the v0.0.5 release You can open the hApp’s dev console by selecting/activating your hApp and then pressing Ctrl+Shift+I. I have just posted a walk-through video that shows this and other features: Holoscape v0.0.5-alpha & Communities install walk-through - YouTube
Regarding the port issue: yeah, I saw that problem before and thought I had fixed it. I see that you’re new interface got the same port that is used for the Peer-Chat interface. In order to recover from this situation you might have to change the conductor config manually (since the conductor will fail to boot from that config next time you start up).
Your bundle file looks good, I think this is just a flaky failure of Holoscape. If you try it again, it might just work.
Generally speaking, I would like to replace these local websocket connections with domain sockets fairly soon, so we don’t have these kinds of problems.
Please let me know if this persists, we might have to fix this before moving to domain sockets then.
3 Likes
Yes @lucksus, the port issue seems to persist. When installing my bundle as the first installed bundle, everything works fine since port 10000 has not yet had been claimed. If I install bundle as bundle no 2 the port is already taken and installation gets stuck.
ps. I posted a PR adding holotxt to the temp hApp index.
pps. I posted a PR to Holoscape allowing html links with target=’_blank’ to be opened by default system browser instead of opening inside Holoscape.
1 Like
I’m unable to run the v0.0.5-alpha release on Mac. Getting the following error:
* Using config path: /Users/erlend/Library/Application Support/Holoscape-default/conductor-config.toml
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmZgpkTS8MyRtqmxpGYqi3knP5ui1Ua8bew1JvzHNfyAa2.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmakmeiLMDFzN54CBUSk2UtvyYEUVdnLB6JPg2LLQ3TTrH.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmWBZ9593cVRXz6cYzQSWFx5DyrNVo55hkXWUssaycSdfv.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmZ1z6SKKeG53RQWwma7k644GUaX2dj4v5HEEGTs8ScRyJ.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmakmeiLMDFzN54CBUSk2UtvyYEUVdnLB6JPg2LLQ3TTrH.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmZgpkTS8MyRtqmxpGYqi3knP5ui1Ua8bew1JvzHNfyAa2.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmZgpkTS8MyRtqmxpGYqi3knP5ui1Ua8bew1JvzHNfyAa2.dna.json
* Unlocking agent keys:
Unlocking key for agent 'Personas & Profiles-agent':
Reading keystore from /Users/erlend/Library/Application Support/Holoscape-default/storage/HcScjJUJZv67Oznmsy9WaMtKuVknabwst8sZaohsbA9kuc3uHhZawHwuq9bk55i
* Error while trying to boot from config: ConfigError("Could not decrypt \'primary_keybundle:sign_key\': ErrorGeneric(\"Invalid SigningKey Blob Format: v0 != v1\")")
* holochain process terminated with exit code 0
I tried reinstalling Holoscape from scratch and rebooted: same error.
Try deleting the Holoscape folders in Application Support.
rm -rf /Users/erlend/Library/Application Support/Holoscape-default
rm -rf /Users/erlend/Library/Application Support/holoscape
Then start again.
1 Like
Thank you for the response and supporting other community members. You are right, the issue could be resolved by deleting the default folder.
I had been running into an issue where I couldn’t unlock the keystore since updating to 0.0.5 and found that running the flush command got me running again.
two things to report currently:
- my current setup (on WSL2) is now taking extra long running npm (like minutes during initialization of holoscape).
- Trying to install the communities app, I get the “Hash of found file is different” failure to install.
Thanks for the tip. I tried that but the problem appears to persist. A longer error message appeared on my last attempt.
Error log
* Using config path: /Users/erlend/Library/Application Support/Holoscape-default/conductor-config.toml Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmZgpkTS8MyRtqmxpGYqi3knP5ui1Ua8bew1JvzHNfyAa2.dna.json Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmakmeiLMDFzN54CBUSk2UtvyYEUVdnLB6JPg2LLQ3TTrH.dna.json Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmWBZ9593cVRXz6cYzQSWFx5DyrNVo55hkXWUssaycSdfv.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmZ1z6SKKeG53RQWwma7k644GUaX2dj4v5HEEGTs8ScRyJ.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmakmeiLMDFzN54CBUSk2UtvyYEUVdnLB6JPg2LLQ3TTrH.dna.json
* Reading DNA from /Users/erlend/Library/Application Support/Holoscape-default/dna/QmZgpkTS8MyRtqmxpGYqi3knP5ui1Ua8bew1JvzHNfyAa2.dna.json
* Unlocking agent keys: Unlocking key for agent 'Personas & Profiles-agent':
* Reading keystore from /Users/erlend/Library/Application Support/Holoscape-default/storage/HcScjJUJZv67Oznmsy9WaMtKuVknabwst8sZaohsbA9kuc3uHhZawHwuq9bk55i
* **INFO** 2020-01-03 15:12:05 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:150* Start accepting passphrase IPC connections on socket...
**DEBUG** 2020-01-03 15:12:05 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:173* Passphrase needed. Using unix socket passphrase service...
**DEBUG** 2020-01-03 15:12:05 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:175* No one connected via socket yet. Waiting...
**DEBUG** 2020-01-03 15:12:06 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:175* No one connected via socket yet. Waiting...
**DEBUG** 2020-01-03 15:12:06 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:175* No one connected via socket yet. Waiting...
**DEBUG** 2020-01-03 15:12:07 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:175* No one connected via socket yet. Waiting...
**DEBUG** 2020-01-03 15:12:07 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 3 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 1812
Lock puid-0-3 1633
Lock puid-0-4 1633
**INFO** 2020-01-03 15:12:07 [ **holochain** ] *crates/conductor_lib/src/conductor/passphrase_manager.rs:157* Passphrase provider connected through unix socket
**DEBUG** 2020-01-03 15:12:07 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:179* We have an open connection to a passphrase provider.
**DEBUG** 2020-01-03 15:12:07 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:189* Sending passphrase request via unix socket...
**DEBUG** 2020-01-03 15:12:07 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:194* Passphrase request sent.
**DEBUG** 2020-01-03 15:12:07 [ **holochain** ] main *crates/conductor_lib/src/conductor/passphrase_manager.rs:196* Reading passphrase from socket...
**DEBUG** 2020-01-03 15:12:08 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 3 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 2816
Lock puid-0-3 2636
Lock puid-0-4 2636
**DEBUG** 2020-01-03 15:12:09 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 3821
Lock puid-0-3 3641
Lock puid-0-4 3641
Lock puid-0-a 1556
**DEBUG** 2020-01-03 15:12:10 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 4827
Lock puid-0-3 4647
Lock puid-0-4 4647
Lock puid-0-a 2561
**DEBUG** 2020-01-03 15:12:11 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 5832
Lock puid-0-3 5652
Lock puid-0-4 5652
Lock puid-0-a 3567
**DEBUG** 2020-01-03 15:12:12 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 6838
Lock puid-0-3 6658
Lock puid-0-4 6658
Lock puid-0-a 4572
**DEBUG** 2020-01-03 15:12:13 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 7840
Lock puid-0-3 7660
Lock puid-0-4 7660
Lock puid-0-a 5574
**DEBUG** 2020-01-03 15:12:14 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 8845
Lock puid-0-3 8665
Lock puid-0-4 8665
Lock puid-0-a 6579
**DEBUG** 2020-01-03 15:12:15 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 9850
Lock puid-0-3 9670
Lock puid-0-4 9670
Lock puid-0-a 7584
**DEBUG** 2020-01-03 15:12:16 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 10851
Lock puid-0-3 10671
Lock puid-0-4 10671
Lock puid-0-a 8586
**DEBUG** 2020-01-03 15:12:17 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 11857
Lock puid-0-3 11677
Lock puid-0-4 11677
Lock puid-0-a 9591
**DEBUG** 2020-01-03 15:12:18 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 12862
Lock puid-0-3 12682
Lock puid-0-4 12682
Lock puid-0-a 10597
**DEBUG** 2020-01-03 15:12:19 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 13868
Lock puid-0-3 13688
Lock puid-0-4 13688
Lock puid-0-a 11602
**DEBUG** 2020-01-03 15:12:20 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 14873
Lock puid-0-3 14693
Lock puid-0-4 14693
Lock puid-0-a 12608
**DEBUG** 2020-01-03 15:12:21 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 15879
Lock puid-0-3 15699
Lock puid-0-4 15699
Lock puid-0-a 13613
* **DEBUG** 2020-01-03 15:12:22 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 16884
Lock puid-0-3 16704
Lock puid-0-4 16704
Lock puid-0-a 14619
**DEBUG** 2020-01-03 15:12:23 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 17884
Lock puid-0-3 17704
Lock puid-0-4 17704
Lock puid-0-a 15619
**DEBUG** 2020-01-03 15:12:24 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 18890
Lock puid-0-3 18710
Lock puid-0-4 18710
Lock puid-0-a 16624
**DEBUG** 2020-01-03 15:12:25 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 19896
Lock puid-0-3 19716
Lock puid-0-4 19716
Lock puid-0-a 17630
**DEBUG** 2020-01-03 15:12:26 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 20901
Lock puid-0-3 20721
Lock puid-0-4 20721
Lock puid-0-a 18636
**DEBUG** 2020-01-03 15:12:27 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 21907
Lock puid-0-3 21727
Lock puid-0-4 21727
Lock puid-0-a 19641
**DEBUG** 2020-01-03 15:12:28 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 22911
Lock puid-0-3 22731
Lock puid-0-4 22731
Lock puid-0-a 20645
**DEBUG** 2020-01-03 15:12:29 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 23916
Lock puid-0-3 23736
Lock puid-0-4 23736
Lock puid-0-a 21651
**DEBUG** 2020-01-03 15:12:30 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 24921
Lock puid-0-3 24741
Lock puid-0-4 24741
Lock puid-0-a 22655
**DEBUG** 2020-01-03 15:12:31 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 25926
Lock puid-0-3 25746
Lock puid-0-4 25746
Lock puid-0-a 23660
**DEBUG** 2020-01-03 15:12:32 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 26931
Lock puid-0-3 26751
Lock puid-0-4 26751
Lock puid-0-a 24666
**DEBUG** 2020-01-03 15:12:33 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 27932
Lock puid-0-3 27752
Lock puid-0-4 27752
Lock puid-0-a 25667
**DEBUG** 2020-01-03 15:12:34 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 28938
Lock puid-0-3 28758
Lock puid-0-4 28758
Lock puid-0-a 26672
**DEBUG** 2020-01-03 15:12:35 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 29943
Lock puid-0-3 29763
Lock puid-0-4 29763
Lock puid-0-a 27678
**DEBUG** 2020-01-03 15:12:36 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 30949
Lock puid-0-3 30769
Lock puid-0-4 30769
Lock puid-0-a 28683
**DEBUG** 2020-01-03 15:12:37 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 31955
Lock puid-0-3 31775
Lock puid-0-4 31775
Lock puid-0-a 29689
**DEBUG** 2020-01-03 15:12:38 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 32960
Lock puid-0-3 32780
Lock puid-0-4 32780
Lock puid-0-a 30695
**DEBUG** 2020-01-03 15:12:39 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 33961
Lock puid-0-3 33781
Lock puid-0-4 33781
Lock puid-0-a 31696
**DEBUG** 2020-01-03 15:12:40 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 34963
Lock puid-0-3 34783
Lock puid-0-4 34783
Lock puid-0-a 32697
**DEBUG** 2020-01-03 15:12:41 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 35964
Lock puid-0-3 35784
Lock puid-0-4 35784
Lock puid-0-a 33699
**DEBUG** 2020-01-03 15:12:42 [ **holochain_locksmith::tracker** ] locksmith_guard_watcher/puid-0-0 *crates/locksmith/src/tracker.rs:116* tracking 4 active guard(s) alive for > 1000ms:
KIND PUID ELAPSED (ms)
Lock puid-0-2 36966
Lock puid-0-3 36786
Lock puid-0-4 36786
Lock puid-0-a 34700
* Error while trying to boot from config: ConfigError("Could not decrypt \'primary_keybundle:sign_key\': ErrorGeneric(\"Invalid SigningKey Blob Format: v0 != v1\")")
* holochain process terminated with exit code 0
But I just wanted to play with the latest version; not blocked on anything important. I’ll just wait until the next release and see then
Thanks bro, sorry just catching up on everything, I haven’t been on here for a while so only just seen this. I had issues getting stuck in bali as you may know and only managed to secure my freedom and escape back to London on 11/11/19 but with zero income and no home it has still been very hard so staying alive has been my main focus… I am currently forced to look for a contract so I have had very little time to work on Our World, HoloNET, or anything HC related I am afraid. 
I hope things change soon, but for now I need to pay back all the debts I incurred on Bali trying to survive.
I put a lot of time an energy into HoloNET, etc to help expose hc to the massive .NET and Unity ecosystems, which will help bring a lot more developers and resources, etc. This will be boosted even more with the .NET HDK. I was hoping to be the hc ambassador within these communities and to be supported from you guys for doing this? I also made it Open Source in the hope to attract devs to help, but I am still waiting for this to happen…
Do you have any tips on how I can attract the much needed devs, funding, resources & support I need? Would be really appreciated thanks.
Also with the OASIS API (what Our World is built on top off) it will help bridge HC to all existing blockchains, existing legacy systems by connecting everything to everything, it is a bit like the CEPTR pluggable protocol… This would act as a stepping stone and migration route for all blockchain DAPP’s etc over to HC…
I had one brief call with Phil and had a brief chat with David Atkinson on mattermost but then nothing, I was ghosted for some unknown reason? I’m guessing they have been really busy but by helping me you will help yourselves massively down the line… 
Im still really excited about HC and KNOW it is the future of the internet and beyond… I am a visionary so I see the future so I never had any dealt about that…
I really wanted to be a core part of it and I KNOW I was meant to be within the divine plan… but things went really sideways last year for some unknown reason…
So who is the best person to talk to about getting more support from hc so I can continue this vital work with HoloNET, .NET HDK, the bridging API’s (OASIS API), etc? I would love to speak to Art @artbrock & Eric @zippy directly, since I feel they would be very excited and supportive of what I am building for them… How can we make this happen?
I know this will be a much better year for us all… I REALLY hope we can now all finally start talking, supporting and working together to push this thing over the line and usher in the new internet, new earth and golden age…
Much love & blessings,
D. 
p.s. When I get a chance I will try out what you have put above and feed back to you ASAP… Really excited to see all the progress you guys have been making with sim2h, the holoports shipping, etc… Keep up the great work!
p.p.s. I’m looking forward to plugging in and testing my shiney new holoport soon… 
1 Like
I realised I should have just tagged Art & Eric in my original post so I just edited it now but not sure if it shows up for them if I edit it after? So just in case I will tag them again here…
I feel if we all work together we can help massively turbo charge hc adoption along with the ecosystem so we can all enjoy the new internet, new earth and new freedoms we all dream off…
A better day is coming my friends…
I feel this year a LOT will change for humanity and I am not just talking about hc…
1 Like