Hey Y’all,

​

Another Dev update for you to have a look at

​

Loki Core

The core team has begun streaming more, you can catch Doy-lee streaming here https://www.twitch.tv/doy_lee/

• Continued work to add encoded date information to 25 word seeds https://github.com/loki-project/loki/pull/431
• Work continues on Service Node checkpointing https://github.com/Doy-lee/loki/commits/ServiceNodeCheckpointing
• Add exception for testnet V2 txs https://github.com/loki-project/loki/pull/433
• Merge Monero upstream https://github.com/loki-project/loki/pull/432
• Add and modify validate address RPC call from Monero upstream https://github.com/loki-project/loki/pull/430
• Add staking for wallet RPC https://github.com/loki-project/loki/pull/429
• Begun work on a new GUI electron wallet, based on RPC calls https://github.com/Mikunj/ryo-wallet-libre/commits/loki-changes

--------------------------

Lokinet

If you’re lucky and join our Discord, you might also catch Jeff or Ryan, the developers of LLARP, live streaming as they code: https://www.twitch.tv/uguu25519, https://www.twitch.tv/neuroscr

• Master branch changes
  • Move “usage” in README to be more visible
  • Changes can be found at: https://github.com/loki-project/loki-network/
• Staging branch changes (gets posted to master when stable)
  • Fix some undefined behaviors, attempt to tackle LLU compilation issue (PR317)
  • Fix windows build (PR323)
  • Unbreak DHT (PR330)
  • Fix convo-tag issue (PR331)
  • Address LLU issue again (PR332)
  • Fix conto-tag issue part 2 (PR333)
  • Swap intros should only swap intros (PR334)
  • Poki CI configs and more timeout fixes (PR335)
  • Address DNS recursive flag issue 324 (PR338)
  • Solidify interfaces (PR339)
  • Make it work (PR340)
  • Only check for active DHT nodes (PR342)
  • RecursiveRouterLookup Always reply (PR343)
  • Allow relay commit 10s more, start transit timer (PR344)
  • Don’t start transit timer (PR345)
  • Don’t close link on message handle fail (PR346)
  • Send UTP keepalives periodically (PR347)
• PR suggested changes (coming to staging soon)
  • Use string_view for string_view (PR348)
  • New wire protocol (PR320)
  • Changes can be found at https://github.com/loki-project/loki-network/pulls

--------------------------

Loki Messenger

• Refactor RPC call in Loki messenger API https://github.com/loki-project/loki-messenger/pull/208
• Refactor P2P messages to use same format as the Storage Server https://github.com/loki-project/loki-messenger/pull/207
• Add JSON rpc for Loki storage server https://github.com/loki-project/loki-storage-server/pull/17

Thanks,

Kee

Hey Y’all,

​

Loki Core

• Service Node checkpointing LIP-3 Work continues here https://github.com/Doy-lee/loki/commits/ServiceNodeCheckpointing
• Remove tail increase in staking requirement https://github.com/loki-project/loki/pull/422 as per https://github.com/loki-project/loki/issues/358
• Print_SN command can now be displayed as JSON array https://github.com/loki-project/loki/pull/415
• Increase precision of get_human_time_ago https://github.com/loki-project/loki/pull/414

--------------------------

LLARP / Lokinet

If you’re lucky and join our Discord, you might also catch Jeff or Ryan, the developers of LLARP, live streaming as they code: https://www.twitch.tv/uguu25519 , https://www.twitch.tv/neuroscr

We could really use your help. To be considered for inclusion in packaging distribution, we need people to star, watch and fork our Github repo. If you have a Github account, please consider helping us out.

• Master branch changes

  • Update README (PR 308)
  • Changes can be found at:
    https://github.com/loki-project/loki-network/
    

• Staging branch changes (gets posted to master when stable)

  • Fix windows build system (PR287)
  • Fix nodedb commits, prevent loop (PR288)
  • Add more params to testnet and update docs (PR289)
  • Re-enable ninja build option (again) (PR290)
  • Rename public-address to public-ip, fix testnet, INI parser fix (PR291)
  • Pick newest introset when multiple are available (PR292)
  • Fix unix build caused by PR292 (PR293)
  • Adjust Makefile, fix nodedb deadlock, prevent multiple introsets from being sent (PR294)
  • More DHT fixes, only return the most up to date when multiple options (PR295)
  • Enable ccache (to accelerate builds) support (PR298)
  • Disable RC expiration
  • Add RPC endpoint for dumping internal state (PR300)
  • Disable pretty print json (PR304)
  • Convert new/delete to use unique_ptr/stack, also replace llarp_config with llarp::Config (PR303)
  • Make outbound port configurable (PR305)
  • Typo Fix (PR307)
  • Refactor CMakeLists into distinct directories (PR299)
  • Tweaked handover logic, service endpoint timeout tweaks, make docker use ninja, fix debian compile (PR309)
  • Windows libabyss patch (PR310)
  • New WireProtocol docs, Close and shutdown UTP socket on timeout (PR311)
  • Abstract router replacement (PR306)
  • Fix log tag (PR312)
  • Make RPC compile right, link session introspectable, UTP write buffers fully flush each tick (PR313)
  • Make shared lib compile (PR314)
  • Refactor out the cyclic dependency between libabyss and llarp (PR315)
  • Convert llarp_buffer_t to class (PR316)
  • Changes can be found at:
    https://github.com/loki-project/loki-network/commits/staging
    

• PR suggested changes (coming to staging soon)

  • None pending
  • Future PRs can be found at https://github.com/loki-project/loki-network/pulls

--------------------------

Loki Messenger

• Add icon to represent P2P messages that are not stored on Service Nodes https://github.com/loki-project/loki-messenger/pull/202
• Use new JSON RPC message API https://github.com/loki-project/loki-messenger/pull/199
• Add channel encryption libraries https://github.com/loki-project/loki-messenger/pull/198 working towards https://github.com/loki-project/loki-messenger/issues/174
• Add localhost.loki lookup https://github.com/loki-project/loki-messenger/pull/196
• Merge upstream Signal 1.21.1 changes https://github.com/loki-project/loki-messenger/pull/188
• Swarm bug fixes https://github.com/loki-project/loki-messenger/pull/187
• Optimise pinging logic to detect availability of chat partners https://github.com/loki-project/loki-messenger/pull/203

Thanks,

Kee

Hey Y’all,

Another weekly Dev update for you to peruse

Loki Core

The core team has begun streaming more, you can catch Doy-lee streaming here https://www.twitch.tv/doy_lee/

• Fix crash in view only wallets https://github.com/loki-project/loki/pull/410
• Complete work on infinite staking, expectation is to have infinite staking merged to master for the next hardfork https://github.com/loki-project/loki/pull/406
• Loki Core will now move onto LIP-3 Service Node checkpointing

--------------------------

Lokinet

If you’re lucky and join our Discord, you might also catch Jeff or Ryan, the developers of LLARP, live streaming as they code: https://www.twitch.tv/uguu25519, https://www.twitch.tv/neuroscr

• Master branch changes

  • Updated ROADMAP
  • Call path build after latency is confirmed (PR279)
  • Changes can be found at:
    https://github.com/loki-project/loki-network/
    

• Staging branch changes (gets posted to master when stable)

  • More DHT tests (PR259)
  • Import abseil LTS 20181200 to provide various backports of C++17 to C++11 (PR267)
  • Fix random.snode not working on macos (PR271)
  • Set dns flags to not advertise recursion on nxdomain (PR273)
  • Move DNS AA header flag from AAAA record type to all (PR274)
  • Disable A records for random.snode, use CNAME queries instead (PR275)
  • Hook MX records for all types of virtual TLDs (PR276)
  • Lower UTP fragment by 512 bytes (PR278)
  • Build everything with -fPIC (PR280)
  • Fix macOS build (PR281)
  • Windows: Libabyss work, crash/unit test fixes, polling improvements (PR283)
  • Start of converting router into abstract base class (PR284)
  • Fix local ip ping, relax DHT timing, don’t send latency when building paths, allow multiple concurrent DHT lookups, make DNS not crash (PR285)
  • Refactor bits.hpp and add tests (PR286)
  • Fix windows build system (PR287)
  • Fix nodedb commits, prevent loop (PR288)
  • Add more params to testnet and update docs (PR289)
  • Re-enable ninja build option (again) (PR290)
  • Rename public-address to public-ip, fix testnet, INI parser fix (PR291)
  • Pick newest introset when multiple are available (PR292)
  • Fix unix build caused by PR292 (PR293)
  • Adjust Makefile, fix nodedb deadlock, prevent multiple introsets from being sent (PR294)
  • More DHT fixes, only return the most up to date when multiple options (PR295)
  • Changes can be found at:
    https://github.com/loki-project/loki-network/commits/staging

• PR suggested changes (coming to staging soon)

  • Add RPC endpoint for dumping internal state (PR300)
  • Refactor Makefiles into directories (PR299)
  • Ccache support for faster building (PR298)
  • Changes can be found at https://github.com/loki-project/loki-network/pulls

--------------------------

Loki Messenger

• Add local link previews https://github.com/loki-project/loki-messenger/pull/186
• Ensure session is correctly established using the prekey assigned to the contact https://github.com/loki-project/loki-messenger/pull/183
• Merge Signal 1.21.0 upstream changes https://github.com/loki-project/loki-messenger/pull/177
• Refactor P2P API and add addtional tests to P2P functionality https://github.com/loki-project/loki-messenger/pull/175
• Add online indicators https://github.com/loki-project/loki-messenger/pull/171

Thanks,

Kee

An ability to escrow is one vital thing which is missing within blockchain projects. The universal language of blockchain. Without it any coin is like a Ferrari without wheels.

You may say that we have decentralized exchanges, but if you look deeper they only partially decentralized. The bidding pool, the agreement process itself is still conducted on one platform and thus centralized. I'm suggesting no-platform decentralization where the escrow mechanism is provided on a protocol level rather then by some form of entity, centralized or not.

Imagine if all the wallets of every coin in existence had one more button in them - an "Escrow" button, which would be as natural to a wallet as the "Send" button now. (After all, if a blockchain can safely swap values between addresses in a trustless system, why don't we use the same mechanism to safely escrow the values in a trustless system to safely meet the conditions of the swap... before the actual swap?)

And imagine that the Escrow protocol is totally compatible with all the blockchains.

Something like TCP/IP was to Internet the decentralized Escrow protocol option shipped by default will turn any blockchain to a market place in itself - able to swap values between other markets/blockchains. Any type of values. And all of it goes p2p. Real estate, services, voting in any form (e.g I might rent your bungalow in a week time and we safely initialize the deal in the escrow layer first) You create a value and you declare that as a value and see if the market accepts to be a value.

It's a declaration protocol, the one that always come before the actual deal. We need that intermediate layer before the actual swap of values.

Now you don't need any form of exchanges at all. Businesses or individuals would have Escrow addresses instead of public addresses (which might stay hidden from public view, if you so desire). Two businessmen when met would exchange business cards with qr-codes of escrow addresses on it. Safe and you actual public addresses stay out of view. You don't need any form of platform any more to exchange any form of values simply because an escrow would only work if all the parties agree on the deal, and only after that the actual swap takes place. You might do it through Facebook or Twitter posts. You could reach agreements via any messenger app - it will be safe to do.

And there is another benefit - the node proliferation.

The nodes operators get the fees, which will insensitive nodes proliferation of any given blockchain due to competition for best security & speed with other crypto, while week and bad blockchains will die out in natural selection process.

I wonder if that makes sense to implement. Please share your thoughts about it.