pull down to refresh

0 sats \ 0 replies \ @harrym 13 Dec \ parent \ on: Stacker News Cowboy Credits Market Depth AGORA
Yep. I wrote that response so you could see all the different events.
You have 3 ways to proceed i think.
- no trade resolution: you can't make a clear order book, lots of original/partial trade offers that never get resolved, maximum manual work
- manual trade resolution: you can make a good order book, but still need to handle all the items i mentioned above.
- automatic trade resolution: high capex, low opex. :)
ALL the items I mentioned in the previous post will need to be handled (sooner or later) in cases 2 and 3 (even partial trades). OTOH, 'handle' may just mean 'process for display' - you said you did some of this to get a continuous price axis and a positive spread.
You could choose case 1, just collect offers and produce order books that will confuse Einstein. :)
This is where you are already with just ten or so trade offers!
I see the problem.
Its expected to be low volume, so minimal effort to get something working. But that means high ongoing maintenance to update trades, execute trades, confirm trades, allow partial trades, etc.
I'm not sure how you want to proceed.
For sure, you will prolly NOT want to be hard coding the orders like that forever. You likely want them out in a db-like file, even if its text, say csv? That would enable order updates more easily.
I'm no javascript guy, but surely there's a simple database module you can call in? With something like that, maybe you need more js that ensures standard format and allows user additions to the order file.
Some thoughts that apply whether you do manual or automatic handling...
Background on exchange order types:
1 spot orders, where a user just specifies the volume and the exchange fills the order starting at the best price (for the user) and then 'next' available (but worse) price etc. until the volume is reached.
2 limit orders, where a user specifies a volume and a limit price and the exchange handles all trades available until the price is reached or the trade is filled.
You're using something like limit orders, except you're not allowing for users to get the best price at the time of execution. For example, I might place an order to buy something at .9 sats and someone else places an order to sell that item at .89, then my order should get filled at .89. That makes your order book look weird, and you (or users) would need to notice then resubmit the trade.
Both types may result in partial order fulfillment. That would also need to be handled.
How would you actually know a trade had been resolved by any two users? They would likely just leave their trade offers in your list unless you hound them.
Looks good! I've been waiting years for a Linux native client as good as Gossip, but with zaps :)
Will make sure to try it when all the good stuff is included next quarter.
I realize this is not a support thread, but ARM seems inappropriate for AMD (install failed anyway).
The X64 version installed but failed setup; I guess this the one that should work.
Should I create a github issue?
There's a lot of work around efficient trade engines (which I have no interest in).
Assuming efficiency is not important tho, I can see a simple scan thru the price range and check/resolve any trades that can be executed. You might need to decide who offered their trade first at any given price i guess.
I have no idea what your programming environment is. Would the code run on SN? A Bash script maybe? Is there a database holding the trade offers?
Perl used to fantastic at handling text only stuff, but noone likes it any more :(
I wanted to try a Linux version, so I just checked the releases.
Will the Debian (Intel) version work on my AMD hardware?
I learnt by looking at normal exchanges (mtgox, bitstamp, bitfinex).
I don't think I ever used anything I could offer as a reference, but there are many youtube traders.
hmm. I did at one time read discussion from when bitfinex was being created - I guess the ideas started becoming clear then.
I'm not a trader, but i did try to get it clear in my head back then.
I just realized you are new to trading, so the useful key words for you would be 'exchange order book'. I just did one that tells way more than you need: https://www.investopedia.com/terms/o/order-book.asp
I'm happy to help if I can.
Are you planning to make the changes to resolve the trades automatically?
If you expect any traffic, manual resolution is out of the question.
I'm obviously not understanding the market mechanics here.
In a normal order book, you would never get a negative spread (overlapping buy/sell orders) coz the exchange would automatically execute the trades.
Is that not happening here?
If it did, your order book would be considerably simpler.
I loved the idea! Went to order one but there's no bitcoin payment option.
That seems to be because they chose Stripe for all payment methods and Stripe doesn't have a bitcoin option. Jesus - this is 2025 guys!
Nice idea, but i have to pass unless someone here has a good suggestion. :(
Yes!
It's difficult to set up a system that will do everything Alby Hub does, so Hub is the choice.
Hub is a bit harder to configure if you set up the free version, but if you pay a lot of that is done for you.
And once you have it set up, connecting it to SN for send/receive is a piece of cake.
All Asimov, ofc.
More recently Daniel Suarez (Daemon and FreedomTM) ...
TV-wise, I've watched the Stargate stuff half a dozen times now. Lol, obsessive.
GENESIS