rippled VS cmake-conan

The bug occurred when a multi-path payment interacted with an AMM synthetic offer, and the synthetic offer required to fulfill the payment exceeded the AMM pool size. In this case, the payment engine attempted to use the single-path strategy to back-out the maximum liquidity available to swap against the pool. Although this condition was properly detected, there was an error on how the payment engine resized the synthetic offer to consume liquidity only up to the AMM size. Instead of using the actual swap rate, which represents the cost of fully swapping one side of an AMM pool, the new synthetic offer’s exchange rate was incorrectly set to the spot exchange rate of the AMM (that is, the rate it takes to execute an infinitesimally sized order). Consequently, an AMM operation that should have been expensive became relatively cheap, effectively violating the constant-product invariant of the pool. In this state, another user could deposit funds into the drained side of the pool, generating a large number of LP tokens and taking ownership of the pool. Now that the fix amendment is active, the team has opened a PR with a unit test demonstrating this behavior.

Explore the XRPL Developers Discord, the XRP Ledger Learning Portal, and the extensive documentation available on XRPL.org. You can also participate in XRPL Community Events and Hackathons to engage with like-minded individuals and stay abreast of the latest developments in the XRPL ecosystem.

fixDisallowIncomingV1: Fixes an issue that occurs with authorized trustlines and the “lsfDisallowIncomingTrustline” flag.

It’s good news for the builders who have been working round the clock. Tools such as AI chatbots will enable developers to quickly receive answers to their queries, speeding up the process from concept to application. AI Chatbots have already become a part of RippleX’s commitment to making blockchain development on the XRP Ledger more accessible and less time-consuming, especially for those new to the field. This approach will not only foster increased innovation on blockchains but could also enhance financial inclusion, making tools more accessible globally.

Currently Rippled 2.0.0 is scheduled to release December 18th, 2023: https://github.com/XRPLF/rippled/milestone/8

The XRPL Accelerator, a program dedicated to nurturing innovation and development on the XRP Ledger, is back with its second cohort of groundbreaking projects. After the success of the inaugural cohort, the Accelerator continues to support entrepreneurs and builders looking to scale their projects on the XRP Ledger.

The third annual Apex Developer Summit was the biggest yet. Held in collaboration with the XRP Ledger Foundation, this event brought together an impressive gathering of over 400 blockchain developers, validators, and XRPL community members in the heart of Amsterdam at the Leonardo Royal Hotel.

Explore the XRPL Developers Discord, the XRP Ledger Learning Portal, and the extensive documentation available on xrpl.org. You can also participate in XRPL Community Events and Hackathons to engage with like-minded individuals and stay abreast of the latest developments in the XRPL ecosystem.

As developers and contributors to the decentralized, open-source XRP Ledger (XRPL), the RippleX engineering team is excited to announce a major breakthrough in the XRPL ecosystem that will revolutionize the way developers build decentralized applications (dApps).

-- The CXX compiler identification is GNU 9.4.0-- The C compiler identification is GNU 9.4.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Setting build type to 'RelWithDebInfo' as none was specified. -- /usr/local/bin/ccache found and enabled -- Downloading conan.cmake from https://github.com/conan-io/cmake-conan -- Conan: Adding cci remote repository (https://center.conan.io) verify ssl (True) usage: conan remote [-h] [-v [V]] {add,auth,disable,enable,list,list-users,login,logout,remove,rename,set-user,update} ... conan remote: error: unrecognized arguments: https://center.conan.io True ERROR: Exiting with code: 2 CMake Error at build/conan.cmake:858 (message): Conan remote failed='2' Call Stack (most recent call first): build/_deps/_project_options-src/src/Conan.cmake:20 (conan_add_remote) build/_deps/_project_options-src/src/Index.cmake:182 (run_conan) build/_deps/_project_options-src/src/DynamicProjectOptions.cmake:132 (project_options) CMakeLists.txt:79 (dynamic_project_options)-- Configuring incomplete, errors occurred! See also "/home/user/Desktop/bitwyre/trading/intermediaries/cram_cpp_v3/build/CMakeFiles/CMakeOutput.log".

Some pure conan options, there's a 2.0 super early developer preview for https://github.com/conan-io/cmake-conan/tree/develop2

https://github.com/conan-io/cmake-conan/tree/develop2 might interest you :) we love feedback

I totally agree with you. Have a look at the new cmake-conan integration using Dependency Provider in the develop2 branch : https://github.com/conan-io/cmake-conan/tree/develop2

I've always used conan together with the conan cmake module

using conan from within cmake you can use this https://github.com/conan-io/cmake-conan, or just write your own execute process way of calling it . https://cmake.org/cmake/help/latest/command/execute_process.html

See https://github.com/conan-io/cmake-conan for a neat wrapper that I use in almost all my projects

I always wanted to try to use cmake-conan so I could let Conan grab all packages but have a neat cmake script being in charge of what gets built when. Also, this would allow me to easily switch between CMake fetchcontent and Conan packages that may or may not be stashed automatically on a local Artifactory server. Secondly, since now all build requirements are stashed on a server and binary reproducible, you could concider adding icecream and ccache into the mix. (Try running a node one of your buildservers for massive speadups with icecream) This however does require a reproducible build environment (by configure script) which conan again is really good in.