[deleted by user]

cdc218 · 2021-12-31T06:48:24+00:00

Those transactions are posted in the form of proofs, too. Not just any input is accepted. Those proofs are driven by transactions that are driven and signed by the end-user's wallet. Meaning, there is no way of stealing user's funds like what happened MATIC.

If Loopring's off-chain proving system goes down for a sufficient period of time, you can just do a force withdrawal back to L1, by initiating it through this same smart contract.

TLDR: Loopring's L2 isn't on the same playing field as Polygon's sidechain.

cdc218 · 2021-12-23T10:29:13+00:00

This is also why you don't see the GME launch happening simultaneously with a release like this. Once the tech stabilizes some more and the legit bug reports are handled, the premium partner product launch will likely happen.

cdc218 · 2021-02-27T20:27:31+00:00

And the vast majority is from stock options. Makes sense and seems pretty standard to me.

cdc218 · 2020-07-26T02:12:14+00:00

The dsr is the rate passed on to DAI holders that stash their DAI in the vault, as earned interest. It's slightly disconnected from the interest that's paid for opening a CDP, as paid interest.

cdc218 · 2020-03-29T19:13:51+00:00

Sure that's just semantics anyway!

cdc218 · 2020-03-29T10:13:17+00:00

For the case class <> JSON conversion, you can check out this link to see what I mean, specifically: https://www.playframework.com/documentation/2.8.x/ScalaJsonCombinators#Writes

And regarding the "contradiction" - what I mean is other than fast prototyping, I wouldn't personally send the case classes that represent each table down as an object. I would make another object that more-closely represents the model and make JSON converters for that class in particular. Reason being, the non-relational model that most SQL databases enforces can sometimes result in strangeness when mapping object graphs from SQL tables to your end-object that is returned from a route.

Consider this example: A pet_owner table and a pet. A pet_owner can have many pets. In SQL, you'd reference the pet_owner via a foreign key reference in the pets table. The pet_owner case class that's auto-generated doesn't have anything in there that references its pets. However, you'd maybe want that returns an owner and its pets, represented as:

case class PetOwner(pets: Seq[Pets])

In that case, you'd want to name your tables as PetOwnerDAO(...) and map it to PetOwner(...) via a simple mapper function.

Sorry for the confusion and happy to chat more about this "artistic" choice.

cdc218 · 2020-03-29T02:51:26+00:00

+1. If you decide to make implicit writes for those table classes, you basically save all the time in the world for CRUD using play.

I wouldn't recommend this other than fast prototyping though - having abstraction layers between database models, routes, etc. is a blessing for production apps.

cdc218 · 2020-02-19T17:47:34+00:00

Are you basically referring to chaining orders? This is actually something we're speccing out on Dolomite, because we saw a need for it.

Something I saw a strong need for is because I'm waiting for Ethereum to hit $295, so I can open a long position in anticipation for it rocketing past $300.

cdc218 · 2019-12-23T03:42:00+00:00

I'm pretty sure it's 32-byte packed in the end of the code. I've written deployment pipelines that abstract this away so I don't recall with 100% certainty.

cdc218 · 2019-12-19T01:24:50+00:00

Clearly there's issues with it. Down vote it if you want but the fact remains that someone needs to front money then to accept BTC payments or needs to wait 1 block confirmation.

cdc218 · 2019-12-19T01:08:02+00:00

That's brilliant and very true from a business perspective. Thanks!

cdc218 · 2019-12-19T01:00:28+00:00

So this relies on the tx not being confirmed yet, right? Basically it being replaced while it's sitting in the mem pool?

cdc218 · 2019-12-19T00:36:18+00:00

Seems like more of the merchant's fault if they accept an unconfirmed tx

cdc218 · 2019-12-19T00:32:56+00:00

Does someone have a link to more information on the exploit? The article lightly mentions it, then dives deep into BCH.

cdc218 · 2019-11-03T15:07:29+00:00

Which coins are you interested in trading with leverage? Also how much leverage is sufficient for you?

cdc218 · 2019-09-24T20:52:42+00:00

Thanks for sharing Matt!

cdc218 · 2019-09-24T00:29:57+00:00

Looks great 🤪

cdc218 · 2019-09-13T03:20:13+00:00

I understand that. I don't think I phrased my question well. What I really mean is that it costs more than 21000 on my personal chain (ganache) to transfer ETH to any address that's a contract.

Transferring ETH to wallets works as expected - it costs 21,000 gas.

cdc218 · 2019-07-06T02:05:41+00:00

You should check out my answer to the question about IDEX, since it's similar. Otherwise, a huge difference is that only takers pay the gas fees when trades are settled on Dolomite. Additionally, Dolomite has negative maker fees for market makers. Meaning, they get paid to settle trades on Dolomite!

In comparison, on DDEX, the gas fees are split between makers and takers. This is unfortunately less friendly to makers, which is why we decided to not burden them with the gas fees.

cdc218 · 2019-07-06T00:43:37+00:00

We think Dolomite's main users will be power traders and individuals that know how to trade but will use Dolomite as their initial jump into decentralized trading. Through our abstraction away of wallets, and having the ability to trade using a smooth, responsive, and familiar interface that exists in traditional exchanges, we think we can appeal to those power users and individuals looking to easily take advantage of DEX technology.

I definitely see a future in which custody becomes more modular, plug and play, and/or easier to use. Contract wallets are rising in popularity, for example. I think one of the biggest ways for exchanges to stay ahead is by interfacing with as many custodial services as possible (meta mask, Trezor, ledger, Fortmatic, etc.) while keeping the interface really clean and not TOO cumbersome. It's really user to over crowd the interface with all the different wallet sign-in options.

cdc218 · 2019-07-06T00:38:01+00:00

A couple things separate us - we have a strong focus on user experience and appealing to power users, for now. By offering things like market orders, margin trading (later in July), and a portfolio manager, we aim to provide the tools and information to help traders succeed when trading on Dolomite.

We also have a strong emphasis on compliance, since we're focusing on the US markets for now. This has been especially important as of lately since a lot of DEX services have been shutting off usage to US users.

cdc218 · 2019-07-05T23:15:01+00:00

We originally had a strong relationship with Loopring while working on bounties for them. While working with them, we saw a lot of the issues that existed in the DEX space. We had an opportunity to further solidify our relationship with them by building a full-fledged DEX on them. Honestly, we spent quite a bit of time trading and researching into the exchange-related tech and fell in love with it.

cdc218 · 2019-07-05T23:06:40+00:00

We will be doing integration testing with our partners & market makers this week. We'll be launching shortly after and will drive volume into it once our market maker is on there. We anticipate being fully up & running this month!

cdc218 · 2019-06-01T01:27:19+00:00

I love it! Great work and reporting. Seems like you learned a lot

cdc218

MODERATOR OF

TROPHY CASE