about summary refs log tree commit diff
path: root/pkgs/applications/blockchains
AgeCommit message (Collapse)AuthorFilesLines
2023-12-12erigon: 2.54.0 -> 2.55.1R. Ryantm1-3/+3
2023-12-09oxen: dropWeijia Wang1-67/+0
2023-12-07Merge pull request #272716 from 0xB10C/2023-13-fix-bitcoin-core-darwin-buildPavol Rusnak1-0/+4
bitcoin: fix darwin builds
2023-12-07bitcoin: fix darwin builds0xb10c1-0/+4
Bitcoin Core requires a MACOSX_DEPLOYMENT_TARGET of 10.13. The current default MACOSX_DEPLOYMENT_TARGET is 10.12.
2023-12-07Merge pull request #272706 from prusnak/bitcoin-knotsPavol Rusnak1-3/+3
bitcoin-knots: 23.0.knots20220529 -> 25.1.knots20231115
2023-12-07bitcoin-knots: 23.0.knots20220529 -> 25.1.knots20231115Pavol Rusnak1-3/+3
2023-12-07Merge pull request #266715 from misuzu/ton-updateRaghav Sood1-2/+5
ton: 2023.06 -> 2023.10
2023-12-07Merge pull request #268846 from r-ryantm/auto-update/exodusRaghav Sood1-2/+2
exodus: 23.10.24 -> 23.11.6
2023-12-07Merge pull request #270238 from emmanuelrosa/sparrow-1.8.1Raghav Sood1-2/+2
sparrow: 1.7.9 -> 1.8.1
2023-12-05ledger-live-desktop: 2.71.0 -> 2.71.1R. Ryantm1-2/+2
2023-11-30Merge pull request #270897 from nepet/update-clightning-v23.11Pavol Rusnak1-3/+8
clightning: 23.08.1 -> 23.11
2023-11-30clightning: 23.08.1 -> 23.11Peter Neuroth1-3/+8
Update to the new release of core lightning. The `--disable-developer` flag got removed on core lightning. Developer builds are now always enabled and can be toggeled at runtime by starting `lightningd` with the option `--developer`. Signed-off-by: Peter Neuroth <pet.v.ne@gmail.com>
2023-11-30Merge pull request #270254 from lourkeur/chia-dropPierre Bourdon5-312/+0
chia: drop
2023-11-30Merge pull request #270234 from emmanuelrosa/bisq-1.9.14-r2Weijia Wang1-14/+16
bisq-desktop: 1.9.12 -> 1.9.14
2023-11-29chia: dropLouis Bettens5-312/+0
2023-11-27Merge pull request #269634 from andresilva/polkadot-1.4.0André Silva2-748/+1612
polkadot: 1.3.0 -> 1.4.0
2023-11-27treewide: add mainProgramh7x430-0/+30
2023-11-26sparrow: 1.7.9 -> 1.8.1Emmanuel Rosa1-2/+2
2023-11-26bisq-desktop: 1.9.12 -> 1.9.14Emmanuel Rosa1-14/+16
2023-11-25fulcrum: 1.9.3 -> 1.9.7R. Ryantm1-2/+2
2023-11-24polkadot: 1.3.0 -> 1.4.0André Silva2-748/+1612
2023-11-23besu: 23.10.0 -> 23.10.2R. Ryantm1-2/+2
2023-11-21ton: 2023.06 -> 2023.10misuzu1-2/+5
Diff: https://github.com/ton-blockchain/ton/compare/v2023.06...v2023.10 Changelog: https://github.com/ton-blockchain/ton/blob/v2023.10/Changelog.md
2023-11-21exodus: 23.10.24 -> 23.11.6R. Ryantm1-2/+2
2023-11-19go-ethereum: 1.13.4 -> 1.13.5R. Ryantm1-3/+3
2023-11-17erigon: 2.53.1 -> 2.54.0R. Ryantm1-3/+3
2023-11-15Merge master into staging-nextgithub-actions[bot]1-3/+3
2023-11-15snarkos: 2.2.1 -> 2.2.4R. Ryantm1-3/+3
2023-11-13Merge remote-tracking branch 'origin/master' into staging-nextFabián Heredia Montiel1-3/+3
2023-11-13op-geth: 1.101301.1 -> 1.101304.0R. Ryantm1-3/+3
2023-11-10Merge staging-next into staginggithub-actions[bot]1-2/+2
2023-11-10ledger-live-desktop: 2.69.0 -> 2.71.0R. Ryantm1-2/+2
2023-11-09Merge staging-next into staginggithub-actions[bot]2-696/+576
2023-11-09Merge pull request #266153 from andresilva/polkadot-v1.3.0asymmetric2-696/+576
polkadot: 1.2.0 -> 1.3.0
2023-11-09lib.systems: elaborate Rust metadataAlyssa Ross1-2/+2
We need this stuff to be available in lib so make-derivation.nix can access it to construct the Meson cross file. This has a couple of other advantages: - It makes Rust less special. Now figuring out what Rust calls a platform is the same as figuring out what Linux or QEMU call it. - We can unify the schema used to define Rust targets, and the schema used to access those values later. Just like you can set "config" or "system" in a platform definition, and then access those same keys on the elaborated platform, you can now set "rustcTarget" in your crossSystem, and then access "stdenv.hostPlatform.rustcTarget" in your code. "rustcTarget", "rustcTargetSpec", "cargoShortTarget", and "cargoEnvVarTarget" have the "rustc" and "cargo" prefixes because these are not exposed to code by the compiler, and are not standardized. The arch/os/etc. variables are all named to match the forms in the Rust target spec JSON. The new rust.target-family only takes a list, since we don't need to worry about backwards compatibility when that name is used. The old APIs are all still functional with no warning for now, so that it's possible for external code to use a single API on both 23.05 and 23.11. We can introduce the warnings once 23.05 is EOL, and make them hard errors when 23.11 is EOL.
2023-11-08polkadot: remove asymmetric from maintainersLorenzo Manacorda1-1/+1
No longer use this package.
2023-11-07polkadot: 1.2.0 -> 1.3.0André Silva2-696/+576
2023-11-06Merge pull request #244298 from oxalica/remove-unusedThiago Kenji Okada1-1/+1
{birdtray,isgx,mycrypto,osu-lazer,stretchly,tree-sitter}: remove oxalica as maintainer
2023-11-05Merge pull request #265635 from erikarvstedt/electrs-0.10.1Pavol Rusnak1-5/+5
electrs: 0.9.13 -> 0.10.1
2023-11-05treewide: drop myself from packages that I don't activily maintainJörg Thalheim1-1/+1
2023-11-05Merge pull request #264281 from r-ryantm/auto-update/exodusOTABI Tomoya1-2/+2
exodus: 23.9.25 -> 23.10.24
2023-11-04electrs: 0.9.13 -> 0.10.1Erik Arvstedt1-5/+5
2023-11-04Merge pull request #264132 from r-ryantm/auto-update/besuWeijia Wang1-2/+2
besu: 23.7.3 -> 23.10.0
2023-11-04Merge pull request #263643 from r-ryantm/auto-update/ergoWeijia Wang1-2/+2
ergo: 5.0.14 -> 5.0.15
2023-10-31fulcrum: 1.9.2 -> 1.9.3R. Ryantm1-2/+2
2023-10-30exodus: 23.9.25 -> 23.10.24R. Ryantm1-2/+2
2023-10-29erigon: fix SIGILL error due to missing CGO_CFLAGSJakub Sokołowski1-0/+5
Currently Erigon binary fails to start on some systems with: ``` > erigon --version Caught SIGILL in blst_cgo_init, consult <blst>/bindinds/go/README.md. ``` The reason for that are missing `CGO_CFLAGS` that can be seen here: https://github.com/ledgerwatch/erigon/blob/v2.53.2/Makefile#L26 For more information on this see this `bsc` issue: https://github.com/bnb-chain/bsc/issues/1521 Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-10-29besu: 23.7.3 -> 23.10.0R. Ryantm1-2/+2
2023-10-28go-ethereum: 1.13.0 -> 1.13.4R. Ryantm1-3/+3
2023-10-27erigon: 2.50.0 -> 2.53.1R. Ryantm1-3/+3