Thanks for explanation, that's answers I was looking for. I'll have a look around project's Discord.

Question no 1: What do you guys gonna do about polymorphic malware? Considering the core of MalwareChain concept (as I have understood it from WP) is about storing hashes of suspicious files on blockchain. I mean, any teenager or noob can and likely will take that extra step if writing malware (dead simple example - picture Windows EXE that updates own resources using Win32 API - so easy to write, and the EXE/DLL can change it's own hash every launch or every minute or whatever). And that's where heuristics have to kick in, system call analysis etc., so I'd be interested in how's that going to be addressed in your project ...

Question no 2: How would you prevent bad actor (eg. me) from running several Discovery nodes, and submitting false matches to your antivirus database, eg. hashes of wallets of competitor's coins or even your own wallet/client, some common Windows DLL etc.? How are the inputs going to be validated, if the DB is supposed to be updated real-time, according to your WP.

No trolling just genuine interest, that's some of the questions I would ask myself if building such a system.

We have an announcement to be made for Bitcointalk community - we have successfully completed another step on our roadmap and launched Veles Core dVPN service for public alpha-testing. More info, guides on how to connect, config files and certificates download (generated for you on the fly by our decentralised certification authority) are available on our official website:

https://www.veles.network/dvpn.en.html

Happy testing and enjoy your new VPN access!

You should have asked on Discord, everyone from the team is active there daily. I was busy launching decentralised VPN for public alpha-testing and didn't check bitcointalk.  Anyway the seed issue should be already fixed, in latest wallet it's DNS-based seed is updated regularly (also re-launched seed coded in old wallet).

The official block explorer that's useless for you is not the only one, the alternative explorer even lets you copy&paste the list with addnode directives... And it's true the masternode list in current block explorer shows output hashes but no IPs, we havent spent any time on changing the old masternode list, because we were waiting for first dVPN and dapp-enabled masternodes launch. Now we're working on a completely new masternode list page (will be ready within a week time ; for curious ones, the new extended masternode list can be pulled through our decentralised API from: https://explorer.veles.network/dapi/mn/list , including IP's or VPN support info).

Seed list on alternative explorer:
https://chainz.cryptoid.info/vls/#!network , look for newest version (0.18.1.3), click "node list" and copy the contents ...

https://imgur.com/qqZxwkA

- Default RPC port is mentioned in the help (if you bother to read it). But sure you can pick any free port (preferabily between 1024 - 65535), and set it with rpcport option in the config. Anyway, if you want know the default port, just search for rpcport info in the help - velesd -help | grep rpcport -A 2.

(If on Windows, open the command line, go to the Veles installation directory, then run veles-qt.exe -help or velesd.exe -help and scroll to the rpcport info. Sorry, I'm not a Windows user, now I see how much harder everything is on Windows).

Anyway, the default is 5493 at least since the version 0.17.

- I had no problems with nodes / connections while testing recent versions, but as Velecore said, you can always add more nodes using "addnode" option in config (or as an rpc command), for example, you can pick some from the masternode list ( http://explorer.veles.network/masternodes ), those don't change IP frequently. There's almost half peta-hash hashrate, and about 200 masternodes, so I think the network is active enough. In the next release we'll include as a seeds DNS records with full masternode list (near to real-time updated records, thanks to Lua-script-based DNS entries).

- To download the latest Veles Core wallet / daemon just visit the official website, or official github, and go to download / releases section ( https://www.veles.network/download.en.html , https://github.com/velescore/veles/releases ). We even provide .deb installation packages for Ubuntu / Debian / Raspbian for simple installation on those systems, and installation script for other distros, or an automated installation wizard for Windows.

Finally we have just been listed on CoinMarketCap. They don't track our market data yet, as at the moment we have sufficient volume only on one exchange listed on CMC, of required minimum of two, but it's still a good news. At least the project can now be found on CMC with all the relevant links and brief description.


And it shows us that we have already passed their Evaluation Framework requirements for listing, just missing the trading volume on at least two CMC-listed exchanges, to have our market data tracked by CMC. Which is, IMO, just fine for the project at this early stage. (Like, Crex24 volume is just fine, but that's it. The Korean exchange Citex - where VLS volume is kind of mad - it's not on CMC, I think because of lot of bots there, or because they incentivize people for trading).

It's actually thanks to link on CMC I just came back to this thread, as we're most active on our Discord channel, there's discussion or updates happening each day. From now on I'll make sure we'll get more active here on BitcoinTalk too.

Since the last update posted here a lot of things has happened and not been announced here, only on Discord / twitter / website - such as the maximum supply reduction from originally planned 12.5m to 2.5m coins, the new website release - with real-time blockchain data served from websocket - now in English, Simplified Chinese, and Spanish... The latest news was that as one of first coins at the moment we've implemented masternodes (and naturally, all other Veles-specific stuff as multi algo, dynamic rewards, our dynamic non-linear halving system etc. on the latest Bitcoin codebase v0.18. The first alpha testing of dVPN for supporters is also not far ahead, as we've successfully  completed our testing of protocol multiplexing (serving VPN + Veles Core node + HTTPS from the same single port) on our dev-net masternodes. Also PoS and Private Send integration is in progress right now. And yea, there's web-wallet just coing out in a couple of days (secure, strictly client-side browser based, with SegWit, MultiSig support, etc.).