aboutsummaryrefslogtreecommitdiff
path: root/content/en/blog/20210320-ouroboros-rina.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/en/blog/20210320-ouroboros-rina.md')
-rw-r--r--content/en/blog/20210320-ouroboros-rina.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/content/en/blog/20210320-ouroboros-rina.md b/content/en/blog/20210320-ouroboros-rina.md
index d16c49f..d50f33e 100644
--- a/content/en/blog/20210320-ouroboros-rina.md
+++ b/content/en/blog/20210320-ouroboros-rina.md
@@ -32,13 +32,13 @@ why Ouroboros exists, and how it's different from RINA.
If you're in a hurry, this is the TL;DR: We spent 4-5 years
researching RINA in EU-funded projects and understand its concepts and
ideas very well. However, we looked beyond the premises and the
-us-vs-them mentality of the RINA community and areas for improvement
-and further simplification. And more than a couple of things in RINA
-that are just plain-old wrong. While RINA insiders may suggest that
-Ouroboros is 'RINA-inspired' or use some other phrasing that
-insinuates our prototype is an inferior design or some watered down
-version of RINA: it is not, to the contrary, Ouroboros is the diamond
-to RINA's graphite.
+us-vs-them mentality of the RINA community and found areas for
+improvement and further simplification. And more than a couple of
+things in RINA that are just plain-old wrong. While RINA insiders may
+suggest that Ouroboros is 'RINA-inspired' or use some other phrasing
+that insinuates our prototype is an inferior design or some watered
+down version of RINA: it is not, to the contrary, Ouroboros is the
+diamond to RINA's graphite.
And a quick note here: Ouroboros _the network prototype_ has no
relation to Ouroboros _the Proof-of-Stake protocol_ in the Cardano