Skip to content

Feat/safe escrow#22

Open
codeicey wants to merge 4 commits intomainfrom
feat/safe-escrow
Open

Feat/safe escrow#22
codeicey wants to merge 4 commits intomainfrom
feat/safe-escrow

Conversation

@codeicey
Copy link
Member

No description provided.

@codeicey codeicey linked an issue Jan 18, 2023 that may be closed by this pull request
Copy link
Contributor

@codynhat codynhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here are two test cases for LigoSafeEscrow

  • should deposit to predicted address
    • Call predict
    • Make native ETH deposit at address
    • Deploy safe at address
    • Check that balance is equal to original deposit
  • should issue refund to paymentReceiver
    • Call predict with paymentReceiver
    • Make native ETH deposit at address
    • Deploy safe at address
    • Check that paymentReceiver received a refund

});
}

private async _wyrePayment(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the Wyre call will require some KYC? Like the person's name and address below.

I'm not sure that this is the best place to integrate with Wyre. What are the different ways to integrate? Do they have their own UI? A whitelabeling option? Does using the API here mean we can have our own UI?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we talked about synchronously, let's just remove Wyre for now.

}

// setup relayer
async setupRelayer() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this just a temporary solution for setting up a relayer?

We may want this to live in the agent. An agent can have their own Infura account and "gas tank".

I also see this in the Infura docs:

Infura Transactions (ITX) is currently undergoing changes and is only supported for existing customers.

Does this mean we can't use ITX as a new customer?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we talked about synchronously, let's just remove ITX for now.

if (!this.#safeFactory) {
throw new Error("LigoSafeEscrow is not connected");
}
const safeAccountConfig: SafeAccountConfig = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both SafeAccountConfig and SafeDeploymentConfig will later need to be given to an agent to do the deployment. These probably could be returned from this function.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deterministic Safe and Deposit

2 participants