I cannot get answers from the OpenSea team about setting royalties in my smart contract itself using standards defined in EIP2981. But OpenSea does not show the royalty in test-net. Can someone please let me know?
Opensea doesn´t support EIP-2981 at the time of writing. I think they will eventually, not sure how long it can take tho.
Related
I am seeing porting options but I know that is no longer needed. I know based on what eztexting and others are offering.
I am looking for documentation or someone to speak with who has made this happen. I appreciate any help.
I have already deployed a contract on the ropsten test network and also have the contract address.
But, How do I interact with it through something like an android project?
I know I have to add the dependencies first and all. But, here's the confusion -
I have deployed the contract on etherscan's ropsten testnet through the remix IDE
Deployed a project on infura
Created a metamask wallet which now has 1 eth on the ropsten testnet
now, how do I combine all this such that I can access it in my android studio or any other project for that matter?
All I need is to know how anybody would interact with a contract.
Even getting to know the basic requirements steps would be more than enough.
Any help will be appriciated...
its getting harder and harder to find answers on the net and I don't have much time. Appriciate the help, thank you...
I somehow found a blog with a Github sample project which is simple enough to figure out what does what inside the project.
It is an extremely simple hello world project.
If you are like me and haven't been able to make any progress for the past 4-6 hours because of lack of info, then this will surely help.
here's the Github Link if you are in a hurry.
Hope everyone is well.
I have read the Chrome Web Store Developer Agreement which I believe has provided clarity on the matter, but just wanted to check with others who may have been down the same route...
Am I correct in thinking if building a paid Chrome Extension that you don't have to accept payment via the Chrome Web Store payment processing?
I ask, not because I want to avoid their 5% fee, but rather, I was looking at using a 'Merchant of Record' such as Paddle, 2Checkout or Fastspring as these services not only act as a payment processor but also obviously act as a reseller and in doing so take on all liability in regards charging, collecting and remitting the necessary sales tax, VAT & GST, therefore making things much easier for me in that regard.
I would greatly appreciate if anybody had any experience with this and could confirm this is possible as I currently believe it is.
Many thanks in advance.
so far so many Dapp developers have made so many Dapps which are integrated with MetaMask or other similar extensions like Parity and Web3.js.
Is there any idea or suggestion about developing one without all those extensions mentioned above ?
Thank you.
There are mostly two reasons these extensions exist:
The user shouldn't need to trust the website to provide their. blockchain data source, and more importantly, users should never have to trust a web app with their account's private key.
Of course you can make sites without those guarantees, but to do that kind of misses the point of decentralizing trust.
I've recently came across a project in alpha: https://fortmatic.com
It gets rid of the need to use DApps without extensions. Docs seems pretty good, was able to get things working pretty fast. It triggers a modal in an iframe for user auth (similar to Stripe or Plaid) - imo this feels like a better ux as the end users never have to leave the main dapp experience
I have a Realtime API application in which the prototype of gapi.drive.realtime.CollaborativeString is modified to provide extra methods. Today (October 30, 2014) at about 10 AM EDT, the app suddenly stopped working. It turns out that accessing gapi.drive.realtime.CollaborativeString.prototype throws an error because gapi.drive.realtime.CollaborativeString, along with all the other Collaborative classes, is now undefined!
I am currently working around this by adding the required methods to each CollaborativeString individually, but I would appreciate if someone on the Google Drive API team could tell me:
Has the API actually been changed today to remove the public handles for these classes?
If so, why?
Most importantly, why was there no warning or change in the documentation? Unless there was no change and I'm just being stupid, this caused significant downtime on a production service today. The documentation still lists the classes in the gapi.drive.realtime namespace.
Thank you in advance for your clarification and sorry for the StackOverflow format. Also posted in the Google Drive issues forum.
We made some changes to the API to avoid exposing obfuscated private properties, which were causing problems for several of our users who were using custom objects (https://developers.google.com/drive/realtime/reference/gapi.drive.realtime.custom).
I'm sorry for the downtime that this caused. We did not know that anyone was modifying the prototype objects, and in fact we never doing so would work at all (though obviously it does).
I would be happy to have a 1-on-1 conversation about your app and how we can prevent future downtime. We have a pre-release channel that I would be happy to whitelist you for so that you can test changes before they affect your production users.