I am trying to deploy a smart contract in remix, I have metamask and my eth balance should be enough (0.21ETH). But I cannot deploy the smart contract with no error display. What should I do.
There are some little configurations have to be set first, please check:
if your link is using http instead of https
if you have logged
in Metamask
if you have turned off the privacy mode in Metamask
Related
i am facing an issue with deploy and interaction with contract on Hyperledger Besu. I have created nodejs api to deploy any type of smart contract, and later interacting with deployed contract.Firstly i had deployed ERC20 contract to Besu network(besu quickstart)using web3.eth.Contracts.deploy method and interacted with same, everything works fine now for the second time when i deploy non-erc20 contract then i am unable to interact with erc20 contract functionalities but able to make calls to non-erc20 contract. Please suggest me resolution.
Need to know if the issue is with the Besu network or the nodejs apis i created
We are planning to implement CDC in our project and Pact is being considered as primary candidate. Currently I am working on a POC to set up end to end flow with CI/CD integration with GitLab. I have couple of questions related to Authentication/Authorization/security.
Consumer - Pact Broker: Consumers here are external partners. I see client side certificates as an option. I am not able to find much documentation or info on Web for the options available. Pact broker will be hosted in AWS. Can we place this behind a gateway?
Pact Broker and Provider: Both components are part of our infrastructure. In this case I understand that we will be generating a GitLab trigger token which will be passed as part of future requests to Provider pipeline. We will be using same token every time.
Could you please advise options available in both cases to make the communication more secure.
Thanks in advance.
We are planning to implement CDC in our project and Pact is being considered as primary candidate.
Good choice! :)
I have couple of questions related to Authentication/Authorization/security
The OSS broker doesn’t have any security controls other than basic auth and read-only/read-write access permissions (which isn’t very appropriate for external use for obvious reasons). There is basic support for redacting credentials in the UI, but you can still get them through API calls (even for read-only accounts).
Consumer - Pact Broker: Consumers here are external partners. I see client side certificates as an option. I am not able to find much documentation or info on Web for the options available. Pact broker will be hosted in AWS. Can we place this behind a gateway?
Where did you see that client certificates were supported? I’m sorry to say that is incorrect.
You can definitely put it behind a gateway/reverse proxy type thing: https://docs.pact.io/pact_broker/configuration/#running-the-broker-behind-a-reverse-proxy
You would need to add your own authentication layer for this purpose, so using a an API gateway for this that might be a good starting point.
Pact Broker and Provider: Both components are part of our infrastructure. In this case I understand that we will be generating a GitLab trigger token which will be passed as part of future requests to Provider pipeline. We will be using same token every time.
The provider side authentication is the same as consumer.
Alternatively, we have created Pactflow, which is a commercial version of the OSS Broker designed for enterprise use which has a full security model wrapped over the OSS broker including API tokens, and secrets, teams management and other useful features (see https://pactflow.io/features/ for more). We are also almost ready release CI users and fine-grained permissions management.
I want to create ERC20 token on azure blockchain service, and want to allow publicly sending ERC20 tokens and checking balances using metamask. However, I want to allow only sending ERC20 tokens, but don't want to allow other administrative operations publicly.
Is it possible to share rpc with such a restricted access right?
You can have only one rpc port and every client connecting to this rpc will have the same right.
You can use IPC to do your administrative operation.
i use AWS Api Gateway and a Lambda function to process Paypal (Ipn) instant notification messages. how can i secure my api gateway to only allow access to the message sent by Paypal which are then passed on to my lambda function. at the moment the api is open to anyone to access and i am afraid of malicious activity triggering the api and lambda function and thus incurring costs on my behalf.
i have secured my other Apis using Cognito and the associated lambda functions using roles and permission policies but don't know how to handle the calls on my ipn api as these will be unauthorized.
okay, managed to sort it out. created a whitelist resource policy for the api and included all the ip addresses for the paypal ipn - i was stumped at first because after creating the whitelist, it did not work. only later found out that i had not included the sandbox ip address. after including that address, it worked.
check out paypal documentation for sandbox: paypal sandbox IP addresses
and live IP addresses: paypal live IP addresses
hope this helps someone
In ethereum, does the contract hosting account (the account where the contract is deployed to) owns the ether that's being sent to the contract? If not then what if contract gets deleted, does the ether gets sent back or just disappear.
A contract is an account. (I think that's sort of what you mean by "contract hosting account?")
So yes, the contract owns its own ether. The only way a contract can be "deleted" is if it calls selfdestruct(target), in which case the remaining ether balance of the contract is transferred to the address given in target.