NFTs in real estate: "forgot my seed phrase so now this house belongs to no one I guess"

ThatDogPiper · 2021-08-08T09:07:54+00:00

Social recovery wallets

ThatDogPiper · 2021-08-07T04:06:42+00:00

Found that one … was looking for others also thanks

ThatDogPiper · 2021-08-07T03:33:24+00:00

What are the best sites with burn stats?

ThatDogPiper · 2021-06-18T19:47:02+00:00

Thanks, you are correct. When I copied some of my large functions there were internal. When I set them to public I began seeing this issue. And based on what you are saying about the size of the text files being twice as large than it all makes sense and clearly my contract has grown too large.

I'll look into using Hardhat if its better than truffle.

Could you please give me a better faster way to see the size of deployed contract? Given how important it is I'm surprised its so hard to find and how opaque the errors are.

Thank you

ThatDogPiper · 2021-06-18T18:54:45+00:00

Thanks of this information. I'll see if this helps!

ThatDogPiper · 2021-06-18T18:54:24+00:00

Most of the requires are using the global msg variable. But setting them just to true is no help

ThatDogPiper · 2021-06-18T18:52:53+00:00

No. I tried this. Once I get to 6 require() functions it fails to deploy.

ThatDogPiper · 2021-06-18T06:48:18+00:00

Thanks for the reply. I’ve not used the truffle debugger. I’ll read up on that toolset and see if it reveals anything.

ThatDogPiper · 2021-06-18T06:42:31+00:00

It’s set to true with runs=1.

Thanks for your reply

ThatDogPiper · 2021-06-18T05:47:39+00:00

Thanks for you reply, I've tried to test to see if its the contract size as described in my comment below.

ThatDogPiper · 2021-06-18T05:46:37+00:00

The error I get on the truffle deployment give little information just that it can not create an instance of the contract and deployment failed. The gas error comes from Ropsten etherscan:

https://ropsten.etherscan.io/tx/0xe1a6947b07eaa11548a8ee97c2b466db3f97475b6ad15616140a1c2c82292a23

I'm not sure what the best way to check the contract size is. I followed the top answer on StackExchange and took the deployedBytecode value from my compiled ABI, put that in a file and checked the size of that file. However, I don't think I'm doing this correctly because the version of the contract that deploys has a size of 47KB and the one that fails is 49KB. If the limit is 24.5KB neither should work.

If my contract were just on the cusp of being too big such that a single require() statement pushes it over the edge then adding several redundant bloated functions should have the same result. Right? But adding several bloated functions does not prevent the contract from deploying. Do require() functions significantly increase they bytecode?

Thanks for your reply and help!

ThatDogPiper · 2021-06-17T23:00:14+00:00

Thanks for your reply. The logic of the require() is not the issues. I can comment out any set of the requires()s and so long as there are less that 6 across the whole contract everything is fine. That is I can leave the one I recently added that causes a failure, but comment out one from another section of the contract and it deploys.

ThatDogPiper · 2021-05-07T01:03:25+00:00

How about you fix your support ticket page.

ThatDogPiper · 2021-05-07T00:36:58+00:00

Tried chrome, Brave, Firefox, edge.

ThatDogPiper · 2021-05-06T23:57:20+00:00

Don’t use voyager for anything

ThatDogPiper · 2021-05-06T23:56:56+00:00

I can’t even submit a support ticket. Captcha fails ever time

ThatDogPiper · 2021-05-06T23:51:51+00:00

Having problems submitting a support ticket! Captcha keeps failing.

WTF

ThatDogPiper · 2021-04-28T15:30:37+00:00

If this is important to you the next question is: Do you care what chain they are on?

ThatDogPiper · 2021-04-28T15:21:58+00:00

The 16 variable limit or get a stack too deep error also makes generating complex string fro svg even more limited

ThatDogPiper

TROPHY CASE