[01:38:16] Is there any reason we arent running a DNS seeder? [04:54:55] we are [04:55:00] i mean, i am [04:58:10] Ahhh [04:58:24] Is there a repo for that? [05:41:03] @aguycalled ^ [07:37:07] https://github.com/NAVCoin/navcoin-seeder [07:37:09] @paul [08:56:35] Ok... Should have looked :) [08:56:51] What is you dns address. [08:57:04] I think I might run one as well. [08:57:41] @aguycalled [08:59:06] seed.nav.community [08:59:12] just add it on chainparams.cpp [10:00:04] on 4.3 When I type ro@nav.community in the GUI send to field it just shows an error. And when I run resolveopenalias ro@nav.community and I jsut get returned js { "dnssec": false, "address": "" } [10:00:23] How are we suppose to send to the open alias addresses? [10:00:42] *** Quits: navcoin-bot (~navcoin-b@nav.community) (Remote host closed the connection) [10:00:58] *** Joins: navcoin-bot (~navcoin-b@nav.community) [12:05:58] Warning: Beginner question ahead. [12:09:50] So I've downloaded the v4.3.0 RC for testing purposes and created an open alias address which is blackheathen@nav.community . From what I've read about Open Alias implementation, this will translate as blackheathen.nav.community, is that correct? Also, does this now replace my standard NavCoin wallet address? [12:10:16] Thanks in advance. [12:21:31] Hi @Blackheathen, nice to hear you're testing the RC, much appreciated. Your OpenAlias will be blackheathen@nav.community and will be associated with the NavCoin address you entered during the registration process on http://openalias.nav.community. You can generate a new address from the core wallet and associate that with a new alias if desired. Payments sent to blackheathen@nav.community as well as any new aliases you create with [12:21:32] generated addresses from your wallet will show up in your transactions history. If you click the RECEIVE menu item and then 'LIST OLD ADDRESSES' you'll be able to see all generated addresses. The default label will be (no label) but you can double click the label field to edit (for example, to keep track of various open alias addresses). [12:24:26] @zanuka Thanks for the comprehensive reply. And I report any bugs found to https://github.com/NAVCoin/navcoin-core/pull/232? [12:26:17] You're welcome. Yes reporting directly to the PR is great and feel free to ask further questions in this channel. [12:28:41] Thanks. I'm happy to support such a great great project. I was inspired by the interview between the Crpto Lark and your man Craig a few days ago but have been following NavCoin for a while. [12:37:48] Apparently Cryptopia is having issues generating new NavCoin addresses ATM. Was trying to send some Nav so I could test sending it back to my open alias address. Here's the Cryptopia error. NavCoin(NAV) Address Error! Unfortunately we are unable to accept your deposit at this time. Failed to generate new address [12:42:10] It appears to be fixed now. [12:44:22] They might have been down for maintenance to update to the new wallet version (my guess) [12:46:51] Ah ok. [13:07:21] So when trying to withdraw 10 Nav from Cryptopia to blackheathen@nav.community I got Invalid NAV address. Am I expecting too much? [13:11:20] yes [13:11:39] they won't support open alias at the moment [13:28:56] Ah ok. Is there another way I can test sending and receiving? [13:39:50] With Open Alias? [13:48:04] You could register two openalias addresses [13:48:09] and try sending to yourself [13:52:09] Will do. [14:17:05] @aguycalled i tried zmq on osx and its worked but on windows its not working. [14:38:48] also on Ubuntu/Linux works [14:40:24] but on windows daemon does not show any errors also nothing on debug.log [14:48:23] https://github.com/bitcoin/bitcoin/issues/7943 [14:52:03] i need zmq on windows for catch messages [14:52:38] i will be happy if you can fix this problem. [15:43:19] Does someone want to try sending a coin or two here? jonathan@nav.community [21:56:59] So good you have you guys testing. We need this for every release! Just leave comments on the PR. Even if everything worked totally fine. And if you came a cross any issues then we really need you to leave a comment as we will fix them all in that branch! [22:00:35] and if you need help commenting on the PR (Pull Request) let us know [22:32:48] @sakdeniz ok ill bring this https://github.com/bitcoin/bitcoin/pull/8238/files to our codebase