• in current go-cyber implementation there is one property
  • which significantly limits utility of cybergraph
  • it is inability to create the same cyberlink second time
  • the protocol return error in this case
  • initially it was done in order to protect cyberank from sybil attacks
  • with formation of knowledge theory
  • its become obvious that two cyberlinks created in different time
  • are fundamentally different cyberlinks
  • allowing this on protocol level we unlock powerful model of usage: eav model
  • in a proposed model cyberrank must be accounted for each unique cyberlink
  • without validation of uniqueness on creation