Iâll remember thanks, do you have some logo that i can put on my website to promote you, something like buildwithmoralis? My website is cyberwealth.pro
How then substitute :
Moralis.initialize(ânsOvHRG0sI17fFwf0CosgwspHnSYxxxâ); // Application id from moralis.io
Moralis.serverURL = âhttps://9c6txxxi.moralis.io:2053/serverâ; //Server url from moralis.io
as to not lunch it from frontend?
ok, but if you compare it with using cloud function to obtain stored API key which of them would be easiest and most secure?
Hi @legenuspl,
In software development, most our important variables are stores in .env files. Based on the environments (development, testing, production) your .env files will change and be hosted in different places respectfully. So, this way is pretty secure and you shouldnât worry about it.
Hope this helps. Let me know if I answered your question.
Have a great day sir.
Thanks Bro, Iâll implement it in my app next version Thanks for sir but call me Mariusz U 2 have a great day!
There are some errors Metamask throws from early as I remember when I started using Moralis:
inpage.js:1 You are accessing the MetaMask window.web3.currentProvider shim. This property is deprecated; use window.ethereum instead. For details, see: https://docs.metamask.io/guide/provider-migration.html#replacing-window-web3
inpage.js:1 MetaMask: The event âcloseâ is deprecated and may be removed in the future. Please use âdisconnectâ instead.
For more information, see: https://eips.ethereum.org/EIPS/eip-1193#disconnect
_warnOfDeprecation @ inpage.js:1
on @ inpage.js:1
inpage.js:1 MetaMask: âethereum.enable()â is deprecated and may be removed in the future. Please use the âeth_requestAccountsâ RPC method instead.
For more information, see: https://eips.ethereum.org/EIPS/eip-1102
I think is the way user = await Moralis.Web3.authenticate(); Moralis handle authentication and communication with MM.
Would these be addressed in future, and moving to new methods?
Hey @legenuspl
Soon the SDK will be redesigned for new web3 methods. Now it doesnât affect the work of web3 functions in any way.
Thanks for nice update. Recently I started getting strange error with some policy I believe:
moralis.js:1 Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep
any ideas?
Also with whom should I speak to have Moralis partnership with my project?
You can take part in #BuiltWithMoralis Program
Im using sdk only:
Moralis.initialize(process.env.MORALIS_API_KEY); // Application id from moralis.io
Moralis.serverURL = process.env.MORALIS_API_SERVER; //Server url from moralis.io
user = await Moralis.Web3.authenticate();
from far as I know i dont use Web3API for authenticate(),
Hi,
Maybe this could help you: https://www.youtube.com/watch?v=2nF76NMQ9JA&ab_channel=MoralisWeb3 if you get CORS errors
Just watching now, its COEP error but I assume you took it into consideration Just a suggestion if you may add link to a source code that would be wonderful as you were doing at early beggingâs I mean on YT
Iâm getting strange error while retrieving PAID price via :
var options = {
address: address_from_info
};
var price = await Moralis.Web3API.token.getTokenPrice(options);
error:
Error: [object Object]
at handleError (RESTController.js:437)
at async makeArrV2 (query.js:473)
all other tokens get correct price, with the same method, is it connected with token address change? Of course I use new SDK to get token address using
await Moralis.Web3API.account.getTokenBalances();
this is response im getting:
- balance: â44500000000000000000â
- decimals: â18â
- logo: âhttps://cdn.moralis.io/eth/0x1614f18fc94f47967a3fbe5ffcd46d4e7da3d787.pngâ
- name: âPAID Networkâ
- symbol: âPAIDâ
- thumbnail: âhttps://cdn.moralis.io/eth/0x1614f18fc94f47967a3fbe5ffcd46d4e7da3d787_thumb.pngâ
- token_address: â0x1614f18fc94f47967a3fbe5ffcd46d4e7da3d787â
and from your SDK it gets correct token address, any ideas?
I did also these steps, someone will contact me or? I would love to announce partnership in future with Moralis
Please open a new thread for price issue, closing this thread as itâs a separate issue
Letâs keep 1 thread = 1 issue so its easy to find solutions for future users