I don't know what that means, but I can list you all platform/architecture combinations we need for
I don't know what that means, but I can list you all platform/architecture combinations we need for now. how is the JNI invocation layer generated?
GI actually mostly agree with @MrStahlfelge . Making binaries for all supported Android platforms would be a PITA.
GSo far, it's in PoC state covering less than 1% of the API and written by hand over the C layer.
TFor the platforms that I mentioned, there's already ready-made instructions to build on it, by inspecting how the CI does it.
TYeah I know very little about android. I can imagine it'll be painful
Mit is not only android (which would mean deploying appkit as an aar built by an own process), but also desktop (windows x86, arm, macos x86, arm, linux x86, arm64, arm32), ios x86/arm (x86 needed for the simulator) - this is 13 different targets, additionally some kind of automated JNI layer generator which is some kind of science on its own etc etc.
GWell, actually you don't need to be connected per se. You just ask a few random nodes some queries.
TRust mostly covers all of the desktop. We're not using any OS-native code to my knowledge. ios is swift-based, so it will span over x86 and arm automatically. JNI, I don't know anything about
GWell, in theory, we really need JNI for Android only. 
Every other platform could use ergo-lib either directly or via its designated layer (Wasm, Swift). I know it's not the point in this case.
Every other platform could use ergo-lib either directly or via its designated layer (Wasm, Swift). I know it's not the point in this case.Mwasm from a Java desktop app? How?
Our current iOS app is done by crosscompiling the Java bytecode. No swift support but cocoapods can be used.
Our current iOS app is done by crosscompiling the Java bytecode. No swift support but cocoapods can be used.
GMore to the point though. All the underlying machinery is already implemented in the node and sigmastate's code. Appkit is just lacking the API that'll tie it all together.
Myeah I think moving the code and exposing it is the far more easy solution for appkit clients but someone with the expertise has to do it
but someone with the expertise has to do itGOh no. I meant if we don't need to work on every platform through the JVM which is not our case. Otherwise, I fully agree with you.
Mgreat. my fear is, we have wallets ready to integrate nipopows but no one has the task assigned to add them to the sdk
my fear is, we have wallets ready to integrate nipopows but no one has the task assigned to add them to the sdkGGitHub
Using NiPoPoW described in KMZ17 Goal Prove that a payment (ERG and/or tokens) was made on the blockchain. EDIT: For a recent payment it would be faster to use UTXO proof described in #502 Step 1. ...
I[ErgoDEX]
- Decentralized matching protocol for ErgoDEX (https://github.com/ergolabs/ergo-dex/blob/de-match/protocols/DeMatch.md)
- Liquidity mining protocol for ErgoDEX (WIP)
- Started implementation of Spectrum Node (side-chain solution for scaling ErgoDEX)
- Fixed swap chart price display
- Swap chart depends on from/to fields now
- Added new ergo side history ui/ux
- Fixed manual refund tx status display
- Added Liquidity page mobile layout
- Fixed Modal window resize behavior
- Transactions queueing (chaining transactions from the UI)
MI would appreciate that a lot
IThat’s great idea! Thanks 
will talk to their team
will talk to their teamGI'll do it tomorrow.
Mwow, if you do it tomorrow that is way faster than expected 
GI meant I'll make an issue detailing workflow and missing parts in appkit.
Mno problem 
Appreciate a spec showcasing how to use it then!
Appreciate a spec showcasing how to use it then!
AAH backend:
- Handling forks
- Now handles unconfirmed txs and avoids double biddings
- User sign in with wallet
- Collection standard implementation WIP
AH UI: - Minting artwork page is added
- New auction page is done
- Artwork specific page is done
- Nautilus is added
LGuapSwap:
- still working on whitepaper/tokenomics
- finished: token allocation, vesting schedule for devs, competitor analysis, main token use case, FIMO (fair initial mining offering) details with getblok, preliminary meeting with UI/UX designer for GuapSwap GUI
- in progress: exploring additional GUAP token use case with GuapSwap PAY and GuapSwap OASIS enabling a potential mechanism for adverting token price deflation via accepting service fees in GUAP and sending them back to the emission contract (i.e. somewhat analogously to how miner fees work)
- working on integrating landing page ui into actual frontend
- using docusaurus for landing page and docs website
- working with cheese to integrate babel fees support into appkit (necessary for guapswap and getblok)
- will be needed for token2token swaps
HExle Update
- Implemented reduced tx for proxy contracts
- Implemented V2 proxy contracts where boxes are created with registers -> This allows us to build a decentralized system
- Integrated a version of ErgoPay within exle to utilize the new reduced Tx
- Fixed up issues within LendBox, and Repayment Box
- Implemented Distribution Repayment Fix
HReally looking forward to this @kb
Do you also have token support on your roadmap? And if so will that include NFTs as collateral?
Do you also have token support on your roadmap? And if so will that include NFTs as collateral?
WWhy do many nodes report 169.254.x.x as IP? I believe when there is no declaredAddress, either the node which doesn't have it or a node that it connects to makes it up, but it looks like a bug to me
WThen again I'm not sure if
null169.254.x.x IPs are reserved
MTake a look in #ergo-watch
Tim trying to run a testnet node but it cant connect to any peers - im running v4.0.35 with
--testnetRunning in testnet network modedo i have to run a different branch to run the testnet? or should i be able to do it off of a normal release?
T/v2/info
Zyou'll need to run 5.0 for testnet now
ZGitHub
5.0.0 RC1 release for testnet.
It has auto-voting for 5.0 soft-fork by default, starting from height 4,096.
Please note, from this release the node has 9021 port for p2p interactions for the testne...
It has auto-voting for 5.0 soft-fork by default, starting from height 4,096.
Please note, from this release the node has 9021 port for p2p interactions for the testne...
Tok is that compatible with v4.x.x? or is that breaking?
Tmostly for mining stuff but api definition etc
Zi believe all the api etc stuff is fine yep, but someone with more knowledge of changes will fill you in i'm guessing
Tok im just doing this so i can have a testnet version of my mining pool, just worried some changes might be implemented in the testnet that arent on mainnet for that
Tbut ty ill at least try with v5.0 and see if i run into issues
Zthere's a #node channel too for all that kind of discussion
Tayy ill ask there if i run into some stuffs
M
Maritsa Art (@maritsaart)
Twitter
•
My new Ergo on-chain ASCII artwork (an ASCIIart+Pixelart technique).
To make this NFT viewable I put pure text in vector format image (svg)
. So svg it's just a container for ASCII art
Tokenart Shark #2
https://t.co/CNPFM0qKuD
@ergoplatformorg
@ErgoFoundation
@SkyHarbor_io
To make this NFT viewable I put pure text in vector format image (svg)
. So svg it's just a container for ASCII art Tokenart Shark #2
https://t.co/CNPFM0qKuD
@ergoplatformorg
@ErgoFoundation
@SkyHarbor_io
7/28/22, 11:11 AM
KBreaking
W(re : <MarantzCube> Take a look in #ergo-watch)
Sir I'm not in discord and what is there for me to see?
Sir I'm not in discord and what is there for me to see?
K@pragmaxim approved but please check comments https://github.com/ergoplatform/ergo/pull/1779#pullrequestreview-1054019053
Pthanks, I will address them ... btw I reviewed and cleaned this one, it could fit into 4.0.36 https://github.com/ergoplatform/ergo/pull/1723
Pdone, I also revisited https://github.com/ergoplatform/ergo/pull/1670 one more time and merged with 4.0.36 ... should be OK
6not really 
. off chain code and contract code are public but the design is not concisely captured in some doc.
would really appreciate your help though .
so will work on putting together some documentation about our design that you can look at.
. off chain code and contract code are public but the design is not concisely captured in some doc.would really appreciate your help though
.so will work on putting together some documentation about our design that you can look at.
CHi All. I setup a Windows ERGO node and it is constantly failing after ~89% sync progress. What do I need to do or look at to get it resolved? The sync just stops. Where can I look to provide details? The first error I see is I get this message.
[ctor.default-dispatcher-6] o.e.l.ErgoStatsCollector - Stats collector got strange input: SemanticallySuccessfulModifier(ADProofs
[ergoref-api-dispatcher-15] o.e.n.wallet.WalletVars - Trying to update prover's parameters, but prover is not initialized
[ctor.default-dispatcher-6] o.e.l.ErgoStatsCollector - Stats collector got strange input: SemanticallySuccessfulModifier(ADProofs
[ergoref-api-dispatcher-15] o.e.n.wallet.WalletVars - Trying to update prover's parameters, but prover is not initialized
WMy V35 node keeps dropping peers like nobody's business....dropping back to V34 to see if that helps.
Anyone else having same issue?? (i can see the main public node only has 30 connection! Usually it's got 100+)...
Anyone else having same issue?? (i can see the main public node only has 30 connection! Usually it's got 100+)...