2018-08-13 00:03:25
@Fireduck Is the exchange backend code going on Github, or are you keeping it closed?
quantumblockz
2018-08-13 00:05:50
closed for now, mostly because the setup is so complicated and I'd hate for someone to lose funds from having it setup wrong
Fireduck
2018-08-13 00:06:05
I don't mind taking the risk myself, but I have a higher standard for software I let others have
Fireduck
2018-08-13 00:11:43
requests.exceptions.ConnectionError
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=9183): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0ddedecfd0>: Failed to establish a new connection: [Errno 111] Connection refused',))
alistar
2018-08-13 00:29:59
work in progress :wink:
Fireduck
2018-08-13 01:00:35
:joy:
alistar
2018-08-13 01:02:23
now just in testnet of SNOW and BCH?
alistar
2018-08-13 01:03:57
Yep
Fireduck
2018-08-13 01:04:13
For testing
Fireduck
2018-08-13 02:05:21
@alistar thoughts on the layout and stuff?
Clueless
2018-08-13 02:56:04
It looks good. How do I move past the first step of entering addresses? Or have you limited it because it's being tested
quantumblockz
2018-08-13 03:04:14
Yeah, where is the enter button? @Clueless
Fireduck
2018-08-13 03:04:37
on the keyboard. >.>
Clueless
2018-08-13 03:05:17
quickly adds the conduit page so you can test it finally
Clueless
2018-08-13 03:06:03
Cool
Fireduck
2018-08-13 03:06:32
okay, there it is
Clueless
2018-08-13 03:06:37
Sometimes I share things prematurely
Fireduck
2018-08-13 03:06:52
I'm going to clean up that page a bit, but I'll leave it functional for the moment.
Clueless
2018-08-13 03:15:24
@Clueless in case it wasn't clear, after putting in the addresses there is no obvious way to continue in making a conduit
Fireduck
2018-08-13 03:15:31
just in case you weren't aware
Fireduck
2018-08-13 03:17:50
grumbles and uncomments out the ugly html additional button
Clueless
2018-08-13 03:18:56
People always up in your shit, wanting things
Fireduck
2018-08-13 03:19:19
Way better than the usual problem, which is no one caring at all
Fireduck
2018-08-13 03:28:01
People should also note, @Fireduck left a script running that backlogged thousands of test transactions. :P
So the test exchange might take awihle hahahaha
Clueless
2018-08-13 03:28:44
Yeah, it is still unburying itself
Fireduck
2018-08-13 04:51:01
So this is the hard part
Clueless
2018-08-13 04:52:25
How to lay this out in a way that explains what the user should do?
The problem is the addresses are pretty long, so doing horizontal layout doesn't look well.
EXCHANGE ADDRESSES, YOUR ADDRESSES
SNOW -> BCH
BCH -> SNOW
Clueless
hey just out of curiosity - i saw that BCH integration was chosen as @Fireduck has lots of old school BTC experience and thus knows how to integrate BCH very easily. but afaik BTC has remained fully backwards compatible, and you dont need to use Segwit addresses if you dont want to. Why no also enable BTC support with almost identical code?
2018-08-13 05:01:53
Rbf, high fees
Fireduck
2018-08-13 05:02:07
Disaster mempool
Fireduck
2018-08-13 05:02:21
~@Lev It adds complexity. We're starting with what we're familiar with first. @Fireduck is doing the backend~
~We have left room to add more on if we choose.~
Clueless
2018-08-13 05:02:28
Doing all trades on chain so a cheaper chain makes sense
Fireduck
2018-08-13 05:02:58
But you are mostly right
Fireduck
2018-08-13 05:03:11
Would be fairly easy to do BTC
Fireduck
i dont buy the "cheaper chain" thing
its almost the same
i dont really think RBF, mempool, or fees make your code any different
literally at all
it may change the usability of the exchange during mempool disaster times
but the code is the same. and by enabling both you avoid the appearance of taking a stance in the debate
2018-08-13 05:05:36
It's funny, I personally like BTC
Clueless
i dont see any reason for snowblossom to be opinionated in BTC vs BCH
2018-08-13 05:06:20
agreed, I prefer to be neutral in what I provide to users. not my place to push them.
Clueless
2018-08-13 05:07:00
The fee might be cheaper right now, but might be very different tomorrow
Fireduck
the participants of this debate are _extremely_ vocal, i'd stay away from taking sides as it may burn snowblossom reputation
although, no such thing as bad press i guess
just my two cents
2018-08-13 05:07:52
but had to pick a pair to trade with
Fireduck
2018-08-13 05:08:04
yeah, you are not wrong about this debate being cancer
Fireduck
2018-08-13 05:08:33
I am hoping people will be interested in how we are going to pay on zero-conf transactions on both sides
Fireduck
i'm certainly interested
imo you should put on an adversarial mindset and try to double spend BCH against frosty
from what i'm hearing BCH is very easy to double spend
2018-08-13 05:09:33
ha, we shall see
Fireduck
2018-08-13 05:09:41
I hear all sorts of dumb things :wink:
Fireduck
2018-08-13 05:09:52
/me is at fault
Clueless
obvious bias given Alex Bosworth is a lightning enthusiast/dev
2018-08-13 05:10:35
Well, Alex can come steal my BCH when we launch.
Fireduck
yup :slightly_smiling_face:
we'll see
if you make a great system and it works, awesome
2018-08-13 05:11:46
@Fireduck If we provide an embedded thing, people can link each other our conduits as a built in payment exchange system.
Clueless
2018-08-13 05:12:12
ha. it will be hard to pay an exact amount
Fireduck
2018-08-13 05:12:18
which is often what is needed
Fireduck
2018-08-13 05:12:50
Basically, if this one store prefers a certain coin, they can provide all their conduits leading to their preferred coin, anyone can pay in any coin and the store winds up with one.
Clueless
2018-08-13 05:23:20
@Lev btw, if you have suggestions about design, or who to talk to , feel free to yell at me. I'm trying to pretty things up.
Clueless
2018-08-13 12:35:18
very oldschool theme for FrostyTrader, I love it.
alistar
2018-08-13 14:57:09
oh hey, the queue has dropped to 0
Clueless
2018-08-13 15:42:58
Yeah just finished this morning
Fireduck
2018-08-13 15:44:56
@Fireduck the design is actually getting a little sexy.
Clueless
2018-08-13 15:46:13
starts on better failure handling
Clueless
2018-08-13 16:42:34
List of things:
• basic pretty error handling
• use monospace font for numbers/input
• getting google fonts local
• cleaning up the css
• improving the templating
• cleaning up the templated data
• reading up on css/html design ideas
Clueless
2018-08-13 16:53:08
All of those are in my opinion lower priority than:
Fireduck
2018-08-13 16:53:23
- Ability to see estimate payments for input amounts
Fireduck
2018-08-13 16:53:39
- More flexible history viewing (more items, more pages)
Fireduck
2018-08-13 17:01:50
hm, agreed.
Clueless
2018-08-13 18:39:52
why would you need the google fonts local @Clueless?
bottob88
2018-08-13 18:40:01
on your develop machine you mean?
bottob88
2018-08-13 18:40:21
only reason I can come up with is so it works offline
bottob88
2018-08-13 18:40:50
in production, I'd want to avoid
• google fonts rate limiting
• google fonts unreliability
• google fonts load time
Clueless
2018-08-13 18:40:52
I think he means not depending on google servers
Fireduck
2018-08-13 18:41:02
yup
Clueless
2018-08-13 18:41:45
80-300ms to load fonts is basically half a second of ugly page / first impression when loading.
Clueless
2018-08-13 18:43:27
For similar thinking, check out how Apple "tricks" users into thinking their apps load faster with screenshots.
1. Take screenshot when app loads fully.
2. On future app starts, Load screenshot instantly at start, while app still loads in background.
3. User thinks it's loaded faster, when they weren't going to touch it for another 2 seconds anyway.
That's pretty legit user hacking though.
Clueless
2018-08-13 18:45:32
People spend time looking at the screen to determine what to do next.
Clueless
2018-08-13 18:46:01
and they are pretty drunk
Fireduck
2018-08-13 18:50:32
yeah ok but think about the people who can have the same webfont already in their browser cache (cause google server)
bottob88
2018-08-13 18:50:38
that way it loads faster :wink:
bottob88
2018-08-13 18:51:22
another way is to put the webfont in the localStorage after the webpage is loaded so it can load quickly from the localStorage the second time a user visits the website / navigates to another page
bottob88
2018-08-13 18:51:44
just sharing thoughts here :slightly_smiling_face:
bottob88
2018-08-13 18:52:41
als enable http/2 (h2) if not enabled by default
bottob88
2018-08-13 20:09:16
@bottob88 most browsers will cache assets by default, I think I'm fine there. I just don't like to rely on other people's servers.
Clueless
2018-08-13 20:09:28
especially for security things.
Clueless
2018-08-13 20:09:45
@Fireduck user custom estimate fields are now in place.
Clueless
2018-08-13 20:10:13
Enter the value of either coin you want to trade for, it tells you what to send.
Clueless
2018-08-13 20:15:53
@Clueless ignore the user facing fluff for now, do the critical stuff like failure handling architecture sculpting first, then data source design like how, what exactly and how to enumerate transactions
it can be quick and pretty, but it only takes only one early vocal user to lose funds to lose trust
it can be ugly and slow and minor nagging is what results at worst, if it works
Rotonen
2018-08-13 20:17:13
i for one am fine with 60s page load times if the thing actually ironclad just works
Rotonen
2018-08-13 20:22:28
@Rotonen
I'm at the point where a lot of my concern is properly communicating information to users.
Specifically making sure the rate is updated asap, that errors are communicated properly.
And honestly, the errors are basically, *the backend is not running* or *the backend is backlogged (which means the rate will have changed by the time your transaction is processed)*
Clueless
2018-08-13 21:26:50
could be i come loaded with all sorts of assumptions of centralized systems like transaction windows and order books
Rotonen
2018-08-13 21:27:38
i suppose those will sorta float in the mem pools of the chain pairs and thus most of the heavy lifting is not something you actually handle
Rotonen
2018-08-13 22:02:33
heh, not quite
Fireduck
2018-08-13 22:02:46
The exchange will act as an immediate counter party to any transaction
Fireduck
2018-08-13 22:02:54
and send out the payment in the other coin immediately
Fireduck
2018-08-13 22:03:13
and adjust the price accordingly accounting for the new pool balances
Fireduck
2018-08-13 22:19:41
in summary, i’m a fish outta water with distributed exchanges
Rotonen
2018-08-13 22:42:02
It isn't a distributed exchange
Fireduck
2018-08-13 22:42:15
Not sure where that came from
Fireduck
2018-08-13 22:50:38
i'm then just outright confused, sorry for the noise
Rotonen
2018-08-13 22:51:36
No trouble. I could see making the exchange software federated and open sourcing it
Fireduck
2018-08-13 23:13:46
List of things:
• ~Ability to see estimate payments for input amounts~ 100% (nice)
• ~basic pretty~ error handling 75%
• ~more flexible history~ viewing 75%
• Test production webserver configuring
• add `How To` and/or `Rate Calculations` pages
• use monospace font for numbers/input
• getting google fonts local
• ~cleaning~ up the css 30%
• ~improving~ the templating 30%
Clueless