off-topic 2018-02-02 | Slack Archive

https://coinmarketcap.com/ <-- theories on what's going on ?

you mean why everything is going down? because bitfinex was using tether to fraudulently pump up markets and they got caught - or that's the current consensus of wht's probably happening

qqq03:02:52

Under that theory, what should be happening to USDT / USD ?

noisesmith04:02:51

USDT would be crashing to zero USD value, the rumors make it sound like they were manufacturing USDT out of thin air with no backing

noisesmith04:02:56

I should hedge what I'm saying here, I'm no expert, I'm just describing what I'm hearing here and there

qqq04:02:10

I must be mis reading something: https://coinmarketcap.com/currencies/tether/ shows USDT losing 0.86% -- less than 1%, while other cryptos are losing > 10%.

qqq04:02:40

@U051SS2EU: Whereas, under the Tether theory, I would expect USDT to crash more than other cryptos.

noisesmith04:02:27

fascinating - could it have to do with the fact that people use tether to transfer between currencies, which might be a step in trying to cash out?

qqq04:02:27

I'm not disagreeing with you on the Tether theory -- I just don't understand how the market is responding.

qqq04:02:09

I dunno. Suppose hypothetically: FooBar owned BTC FooBar believed USDT was going to 0. FooBar wanted USD. Why would FooBar do "BTC -> USDT" ? It seems FooBar would do "local bitcoin exchange" or "buy stuff on newegg" or "gdax / coinbase."

noisesmith04:02:41

right, but if they have FooCoin, and realize all the coins are headed down and just want to cash out, wouldn't one path involve FooCoin -> USDT -> USD ?

noisesmith04:02:45

maybe that's wrong

noisesmith04:02:19

I was under the impression most tether holders were using it mid transaction between harder to liquidate currencies

joelsanchez16:02:21

now I know what not to do.

schmee16:02:31

you’re syntax-quoting syntax quotes 😄

schmee16:02:47

you get some sort of combinatorial explosion when you do that

bronsa16:02:51

heh, yeah

bronsa16:02:03

you get a stackoverflow after 6 or 7 nested syntax-quotes IIRC

bronsa16:02:30

even better

user=>

[]
CompilerException java.lang.RuntimeException: Method code too large!, compiling:(NO_SOURCE_PATH:0:0)
user=>

schmee16:02:46

haha, now that’s an error you don’t see every day

bronsa16:02:20

I wish I could say that :) unfortunately I do enough weird stuff in clojure that it’s not too uncommon to see that once a month for me

schmee16:02:10

I wish I was doing stuff with clojure that made me see that error 🙂

andy.fingerhut16:02:50

Be careful what you wish for. 🙂 In some cases, seeing that error is a sign of problems that are not easy to fix.

andy.fingerhut17:02:57

If I recall correctly, Eastwood using tools.reader and tools.analyzer, keeping extra metadata on Clojure code than the normal reader/analyzer does, causes that exception to occur when analyzing some Clojure code out in the wild, that doesn't give that error if you compile it with Clojure.

bronsa17:02:40

yep

bronsa17:02:55

IIRC it was some code with very big constants

bronsa17:02:21

and being constants inlined in bytecode, it was causing the method to exceed the maximum code size

bronsa17:02:32

by constants i mean EDN literals in this case

jgh18:02:45

dont add the `

2018-02-02

Channels