The most updated version of the smart contract (on the master branch) must be directly open in the EcoLab just clicking a link.

Data validation of the bid value is made with variable type byte (L.216) while the argument for the function Bid is provided as BigInteger (L.224).

Is it ok to use the former on this way to limit its size and keep the latter as is to be compliant with NEO VM variables format?

To fix:

• The orange color is so bright with the white background.

To improve:

• Flowchart images.

• Step-by-step guide to copyright in images online
• How to use the internet images legally

• List of publications related to the project.
• The way contributors show up.
• Link to personal portfolio (tech writer).

Following steps

• Activate your GitHub repositories
• Add a .travis.yml file to your repository
• Trigger your first build
• Understand this...

The analysis of C# is not working right. There are missing configs.

File e9dc768

The crucial classification between ID's created by the MTEsm and by NEO blockchain can be set by the type of the variable. While the former is defined as string, the latter is byte[].
However, they can be easily interchangeable when the variable is passed as object, and all the evaluations defined so far does not reach a good outcome.

For instance, the current method to distinguish them (box code below) considers the input variable object as type string, and checks the first letter of the variable. So, if the member address APLJBPhtRg2XLhtpxEHd6aRNL7YSLGH2ZL is correctly invoked, i.e., the variable is passed on the Main() as a scripthash equal to 52eaab8b2aab608902c651912db34de36e7a2b0f, the function evaluates the hash as Rê«�*«`��ÆQ�-³Mãnz+�. Consequently, the result is wrong.

Other alternative is to evaluate the size of the variable. Such as the commit b44cd74 has tried to do (reproduced below).
Again, the output may be wrong, since a variable like RT9vtMQDGVS5uKFD4bLLChXEKAcPLh, which corresponds to a referendum ID (i.e. a string), could be evaluated as a byte[] with scripthash equal to aa49805a44e08e67c0c5f92da3d21fdbba829416, and then the size of the variable will be 20 too.

With this in mind, what the main difference between this variables?

The code still have a lot of minor bugs and decisions waiting to be fixed. At commit ecd4b01 there are 25 --PENDING-- "tags". The list below tracks all of them accordingly with different scopes:

Business subjects

• :53 Define the factor between 1kW and 1SEB. And then, review at PowerUP() last operations if its right (pay attention to units).
• :935 Review calculation of 'tokens' (pay attention to units).
• :938 Review calculation of 'quota' (pay attention to units).
• :1319 When refunding a member, the Trade() unit is SEB or R$? Is there missing some more operation?
• :1326 Why delete a crowdfunding process data when its not succeeded? Why not keep this information?

NEO API feature

• :62 How to identify the smart contract caller?
• :112 Dependent on the caller address.

Lack of expertise on coding

• :77 How to guarantee to the first contract invoker (the contract owner) to automatically be the first member? How to allow this operation to happen only once?
• :95 CheckWitness requires a variable of type byte[] but members' address are being registered as string.
• :128 CheckWitness requires a variable of type byte[] but members' address are being registered as string.
• :144 CheckWitness requires a variable of type byte[] but members' address are being registered as string.
• :169 CheckWitness requires a variable of type byte[] but members' address are being registered as string.
• :306 Review dataset of each 'key' after the modifications made on the storage configuration. 'Key' is of type string and might represent the ID of a member, a PP or a Referendum.
• :834 Should split the variable 'notes' to get further information.

Missing code validation

• :231 Test second argument of Change() because of its length (array of arrays).
• :712 Test variable convertion.
• :714 Test variable convertion.
• :753 Something to review when updating a member registration data. ("missing dependency"?)
• :793 Something to review when updating a PP data. ("missing dependency"?)
• :1048 Review how to definitely remove a member data from the private storage.
• :1160 Review how to definitely remove a PP data from the private storage.
• :1193 Review what variable type is returned from GetRef(). byte[] or object? This influences on other operations along the smart contract.
• :1251Review what variable type is returned from UpCrowd(). byte[] or object? This influences on other operations along the smart contract.
• :1257 Review what variable type is returned from UpBid(). Should it return something?
• :1271 Still missing to update other 'crowd' values (!?) when doing a UpBid().

The NeoCompiler automatic identifies all the functions and variables defined as public and displays an invoke option to it following the order they appear on the algorithm.

However, how can it confuse a user to select the right operation described on the smart contract through the Main?

1. May an address be differently invoked depending on the function used? In other words, sometimes the variable is passed as a byte[] (hexstring), and sometimes as string(Base58).
   Does it hurt usability?

2. How can I use the CheckWitness and evaluate if the address is a member at the same time?

microgrid-dapp/neo-dapp/microgrid-dapp.cs

Lines 235 to 236 in 506dadd

	if ( (((string)args[1])[0] != 'A') || (((string)args[1]).Length == 0) )
	throw new InvalidOperationException("Provide a valid destiny address.");

3. May I use the dual behaviour of an Address at the same invoke function with a conversion such as .AsByteArray()? Or an explicit conversion like the below is enough?

microgrid-dapp/neo-dapp/microgrid-dapp.cs

Lines 235 to 239 in 506dadd

	if ( (((string)args[1])[0] != 'A') || (((string)args[1]).Length == 0) )
	throw new InvalidOperationException("Provide a valid destiny address.");
	if ( GetMemb((byte[])args[1]).AsString().Length != 0 )
	throw new InvalidOperationException("The address you are transaction to must be a member too.");

All the statements made so far that use the operator is to evaluate a string against an object are wrong, since is evaluates if one variable can be converted to the other (ref). Therefore all the clauses must be rewrote to keep the algorithm behaviour reliable.

In total, there are 6 cases concerning this, and all of them share the attribute of testing an object "id". In summary, they can be found at:

1. Discern PPid (string) and address (byte[]). — operation option change
   

   microgrid-dapp/neo-dapp/microgrid-dapp.cs

   Line 281 in 12f35f8

   if ( (args[0] is string) & (((string)args[0])[0] == 'P') ) // Should be a PP ID.

2. Discern the change of a bid (BigInteger) to other PP change operations (string) — operation option change
   

   microgrid-dapp/neo-dapp/microgrid-dapp.cs

   Line 289 in 12f35f8

   if ( !(opt[0] is string) )

3. Discern PPid (string), Refid (string) and address (byte[]) — function Summary()
   

   microgrid-dapp/neo-dapp/microgrid-dapp.cs

   Line 407 in 12f35f8

   if (!(id is string))

4. Discern PPid (string) and address (byte[]) — function Change()
   

   microgrid-dapp/neo-dapp/microgrid-dapp.cs

   Line 546 in 12f35f8

   if (!(id is string))

5. To limit the change of a member profile data (string, up to personal decision) to a member registration data (BigInteger, upon request to the group) — function Change()
   

   microgrid-dapp/neo-dapp/microgrid-dapp.cs

   Line 550 in 12f35f8

   if ( opts[1] is string )

   
   

   microgrid-dapp/neo-dapp/microgrid-dapp.cs

   Line 559 in 12f35f8

   if ( opts[1] is BigInteger )

6. Discern PPid (string) and address (byte[]) — function ShowContributedValues()
   

   microgrid-dapp/neo-dapp/microgrid-dapp.cs

   Line 1016 in 12f35f8

   if (lookForID is string) // --PENDING!-- não sei se isso vai funcionar direito!

Reorganize the algorithm by the structure of 'classes' in order to provide inheritance and better readability.

😉 Get note from here.

• e4a9398#r35343322
• e4a9398#r35343346
• 15715fe#diff-dcdf0083746db9dec50372e3a276f2b6